View AR0542MBSC25SUD20_8882565.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

? semiconductor components industries, llc, 2011 march, 2017 ? rev. 8 1 publication order number: ar0542/d ar0542 ar0542 1/4\inch 5 mp cmos digital image sensor general description the on semiconductor ar0542 is a 1/4-inch cmos active-pixel digital image sensor with a pixel array of 2592 (h) x 1944 (v) (2608 (h) x 1960 (v) including border pixels). it incorporates sophisticated on-chip camera functions such as windowing, mirroring, column and row skip modes, and snapshot mode. it is programmable through a simple two-wire serial interface and has very low power consumption. the ar0542 digital image sensor features on semiconductor?s breakthrough low-noise cmos imaging technology that achieves near-ccd image quality (based on signal-to-noise ratio and low-light sensitivity) while maintaining the inherent size, cost, and integration advantages of cmos. the ar0542 sensor can generate full resolution image at up to 15 frames per second (fps). an on-chip analog-to-digital converter (adc) generates a 10-bit value for each pixel. features ? low dark current ? simple two-wire serial interface ? auto black level calibration ? support for external led or xenon flash ? high frame rate preview mode with arbitrary down-size scaling from maximum resolution ? programmable controls: gain, horizontal and vertical blanking, auto black level offset correction, frame size/rate, exposure, left?right and top?bottom image reversal, window size, and panning ? data interfaces: parallel or single/dual lanes serial mobile industry processor interface (mipi) ? on-die phase-locked loop (pll) oscillator ? bayer pattern down-size scaler ? superior low-light performance ? integrated position and color-based shading correction ? 7.7 kb one-time programmable memory (otpm) for storing shading correction coefficients of three light sources and module information ? extended flash duration that is up to start of frame readout ? on-chip vcm driver applications ? cellular phones ? digital still cameras ? pc cameras ? pdas www. onsemi.com see detailed ordering and shipping information on pag e3 of this data sheet. ordering information
ar0542 www. onsemi.com 2 table 1. key performance parameters parameter value optical format 1/4-inch (4:3) active imager size 3.63 mm (h) x 2.72 (v):4.54 mm diagonal active pixels 2592 (h) x 1944 (v) pixel size 1.4 m x 1.4 m chief ray angle 25.0 color filter array rgb bayer pattern shutter type electronic rolling shutter (ers) input clock frequency 6?27 mhz maximum data rate parallel 84 mbps at 84 mhz pixclk mipi 840 mbps per lane frame rate full resolution (2592 x 1944) 15 fps 1080p 19.8 fps (100% fov , crop to 16:9) 30 fps (77% fov, crop to 16:9) 720p 30 fps (98% fov, crop to 16:9, bin2) 60 fps (98% fov, crop to 16:9, skip2) vga (640 x 480) 60 fps (100% fov, bin2skip2) 115 fps (100% fov, skip4) adc resolution 10-bit, on-die responsivity 0.82 v/lux-sec (550 nm) dynamic range 66 db snr max 36.5 db supply voltage digital i/o 1.7 ? 1.9 v (1.8 v nominal) or 2.4 ? 3.1 v (2.8 v nominal) digital core 1.15 ? 1.25 v(1.2 v nominal) analog 2.6 ? 3.1 v (2.8 v nominal) digital 1.8 v 1.7 ? 1.9 v (1.8 v nominal) power consumption full resolution parallel: 288.2 mw at 70 c (typ) mipi: 215 mw at 70 c (typ) standby* 25 w at 70 c (typ) package bare die operating temperature ?30 c to +70 c (at junction) *hard standby by pulling xshutdown low.
ar0542 www. onsemi.com 3 ordering information table 2. available part numbers part number product description orderable product attribute description AR0542MBSC25SUD20 5 mp 1/4? cis rgb bare die ar0542mbsc25sufad ? gevk 5 mp 1/4? cis dk demo kit ar0542mbsc25sufah ? gevb 5 mp 1/4? cis hb headboard functional overview the ar0542 is a progressive-scan sensor that generates a stream of pixel data at a constant frame rate. it uses an on-chip, phase-locked loop (pll) to generate all internal clocks from a single master input clock running between 6 and 27 mhz. the maximum pixel rate is 84 mp/s, corresponding to a pixel clock rate of 84 mhz. a block diagram of the sensor is shown in figure 1. figure 1. block diagram active ? pixel sensor (aps) array analog processing adc scaler limiter shading correction fifo timing control control registers data out two-wire serial interface sync signals the core of the sensor is a 5 mp active-pixel array. the timing and control circuitry sequences through the rows of the array, resetting and then reading each row in turn. in the time interval between resetting a row and reading that row, the pixels in the row integrate incident light. the exposure is controlled by varying the time interval between reset and readout. once a row has been read, the data from the columns are sequenced through an analog signal chain (providing offset correction and gain), and then through an adc. the output from the adc is a 10-bit value for each pixel in the array. the adc output passes through a digital processing signal chain (which provides further data path corrections and applies digital gain). the pixel array contains optically active and light-shielded (?dark?) pixels. the dark pixels are used to provide data for on-chip offset-correction algorithms (?black level? control). the sensor contains a set of control and status registers that can be used to control many aspects of the sensor behavior including the frame size, exposure, and gain setting. these registers can be accessed through a two-wire serial interface. the output from the sensor is a bayer pattern; alternate rows are a sequence of either green and red pixels or blue and green pi xels. the offset and gain stages of the analog signal chain provide per-color control of the pixel data. the control registers, timing and control, and digital processing functions shown in figure 1 are partitioned into three logical parts: ? a sensor core that provides array control and data path corrections. the output of the sensor core is a 10-bit parallel pixel data stream qualified by an output data clock (pixclk), together with line_valid (lv) and frame_valid (fv) signals. ? a digital shading correction block to compensate for color/brightness shading introduced by the lens or chief ray angle (cra) curve mismatch. ? additional functionality is provided. this includes a horizontal and vertical image scaler, a limiter, a data compressor, an output fifo, and a serializer. the output fifo is present to prevent data bursts by keeping the data rate continuous. programmable slew rates are also available to reduce the effect of electromagnetic interference from the output interface. a flash output signal is provided to allow an external xenon or led light source to synchronize with the sensor exposure time.
ar0542 www. onsemi.com 4 pixel array the sensor core uses a bayer color pattern, as shown in figure 2. the even-numbered rows contain green and red pixels; odd-numbered rows contain blue and green pixels. even-numbered columns contain green and blue pixels; odd-numbered columns contain red and green pixels. figure 2. pixel color pattern detail (top right corner) black pixels column readout direction . . . ... row readout direction b gr gb r b gr gb r b gr first clear active pixel (44, 43) b gr gb r b gr gb r b gr operating modes by default, the ar0542 powers up with the serial pixel data interface enabled. the sensor can operate in serial mipi mode. this mode is preconfigured at the factory. in either case, the sensor has a smia-compatible register interface while the two-wire serial device address is compliant with smia or mipi requirements as appropriate. the reset level on the test pin must be tied in a way that is compatible with the configured serial interface of the sensor, for instance, test = 1 for mipi. the ar0542 also supports parallel data out in mipi configuration. t ypical configurations are shown in figure 3, note 15, and figure 4. these operating modes are described in ?control of the signal interface?. for low-noise operation, the ar0542 requires separate power supplies for analog and digital. incoming digital and analog ground conductors can be tied together next to the die. both power supply rails should be decoupled from the ground using capacitors as close as possible to the die. caution: on semiconductor does not recommend the use of inductance filters on the power supplies or output signals.
ar0542 www. onsemi.com 5 figure 3. typical configuration: parallel pixel data interface note: pixclk lin e_valid analog power digital core power digital io power digital reg_in 1.8v power extclk reset_b ar xshutdown test from controller s data s clk 1.5 k 1.5 k digital io power master clock (6 ? 27 mhz) digital ground analog ground digital core power digital 1.8 v power 0.1 f 0.1 f 0.1 f frame_v alid to controller analog power 1.0 f 0.1 f v dd _io v dd _tx v dd _pll v dd v aa v aa _pix reg_in reg_fb reg_out d out [9:0] d gnd a gnd 1. all power supplies must be adequately decoupled. 2. on semiconductor recommends a resistor value of 1.5 k , but a greater value may be used for slower two-wire speed. this pull-up resistor is not required if the controller drives a valid logic level on s clk at all times. 3. v dd _io can be either 1.8 v (nominal) or 2.8 v (nominal). if v dd _io is 1.8 v, v dd _io can be tied to digital reg_in 1.8 v 4. v aa and v aa _pix must be tied together. 5. v dd and v dd _pll must be tied together 6. the serial interface output pads can be left unconnected if the parallel output interface is used. 7. on semiconductor recommends having 0.1 f and 1.0 f decoupling capacitors for analog power supply and 0.1 f decoupling capacitor for other power supplies. actual values and results may vary depending on layout and design considerations. 8. test can be tied to d gnd (device id address = 0x20) or v dd _io (device id address = 0x6c). 9. v dd _tx and reg_in must be tied together. 10. refer to the power-up sequence for xshutdown and reset_bar control. 11. the frequency range for extclk must be 6 ? 27 mhz. 12. v pp , which can be used during the module manufacturing process, is not shown in figure 3. this pad is left unconnected during normal operation. 13. vcm_isink and vcm_gnd, which can be used for internal vcm af driver , are not shown in figure 3. vcm_isink must be tied to the vcm actuator and vcm_gnd must be tied to the d gnd when the internal vcm is used. these pads are left unconnected if the internal vcm driver is not used. 14. the gpi[3:0] pins, which can be either statically pulled high/low to be used as module ids, or they can be programmed to perform special functions (trigger, oe_bar, s addr , standby) to be dynamically controlled, are not shown in figure 3. 15. the flash, which can be used for flash control, is not shown in figure 3.
ar0542 www. onsemi.com 6 figure 4. typical configuration: serial dual-lane mipi pixel data interface note: master clock (6?27 mhz) s data s clk test extclk digital ground analog ground digital 1.8 v power digital core power clk_n data1_n clk_p data0_p data1_p data0_n xshutdown digital i/o power 1.5 k 1.5 k analog power to controller reset_bar digital 1.8 v power digital core power 0.1 f 0.1 f digital io power 0.1 f analog power 1.0 f 0.1 f v dd _io v dd _tx v dd _pll v dd v aa v aa _pix reg_in reg_fb reg_out d gnd a gnd 1. all power supplies must be adequately decoupled. 2. on semiconductor recommends a resistor value of 1.5 k , but a greater value may be used for slower two-wire speed. this pull-up resistor is not required if the controller drives a valid logic level on s clk at all times. 3. v dd _io can be either 1.8 v (nominal) or 2.8 v (nominal). if v dd _io is 1.8 v, v dd _io can be tied to digital 1.8 v power. 4. v aa and v aa _pix must be tied together. 5. v dd and v dd _pll must be tied together 6. the serial interface output pads can be left unconnected if the parallel output interface is used. 7. on semiconductor recommends having 0.1 f and 1.0 f decoupling capacitors for analog power supply and 0.1 f decoupling capacitor for other power supplies. actual values and results may vary depending on layout and design considerations. 8. test must be tied to v dd _io for mipi configuration (device id address = 0x6c). 9. v dd _tx and reg_in must be tied together. 10. refer to the power-up sequence for xshutdown and reset_bar control. 11. the frequency range for extclk must be 6 ? 27 mhz. 12. v pp , which can be used during the module manufacturing process, is not shown in figure 4. this pad is left unconnected during normal operation. 13. vcm_isink and vcm_gnd, which can be used for internal vcm af driver, are not shown in figure 4. vcm_isink must be tied to the vcm actuator and vcm_gnd must be tied to the dgnd when the internal vcm is used. these pads are left unconnected if the internal vcm driver is not used. 14. the gpi[3:0] pins, which can be either statically pulled high/low to be used as module ids, or they can be programmed to perform special functions (trigger, oe_bar, s addr , standby) to be dynamically controlled, are not shown in figure 4. 15. the flash, which can be used for flash control, is not shown in figure 4. from controller
ar0542 www. onsemi.com 7 signal descriptions table 3 provides signal descriptions for ar0542 die. for pad location and aperture information, refer to the ar0542 die data sheet. table 3. signal descriptions pad name pad type description extclk input master clock input, 6?27 mhz. reset_bar input asynchronous active low reset. when asserted, data output stops and all internal registers are restored to their factory default settings xshutdown input asynchronous active low reset. when asserted, data output stops and all internal registers are restored to their factory default settings. this pin will turn off the digital power domain and is the lowest power state of the sensor s clk input serial clock for access to control and status registers gpi[3:0] input general purpose inputs. after reset, these pads are powered-down by default; this means that it is not necessary to bond to these pads. any of these pads can be configured to provide hardware control of the standby, output enable, s addr select, and shutter trigger functions on semiconductor recommends that unused gpi pins be tied to d gnd , but can also be left floating test input enable manufacturing test modes. connect to v dd _io power for the mipi-configured sensor s data i/o serial data from reads and writes to control and status registers vcm_isink i/o connected to vcm actuator. 100 ma max. 3.3 v max vcm_gnd i/o connected to d gnd reg_out i/o 1.2 v on-chip regulator output node reg_in i/o on-chip regulator input node. it needs to be connected to external 1.8 v reg_fb i/o this pad is receiving the 1.2 v feedback from reg_out. it needs to be connected to reg_out data0_p output differential mipi (sub ? lvds) serial data (positive) data0_n output differential mipi (sub ? lvds) serial data (negative) data1_p output differential mipi (sub ? lvds) serial data 2nd lane (positive) can be left floating when using one-lane mipi serial interface data1_n output differential mipi (sub ? lvds) serial data second lane (negative) can be left floating when using one-lane mipi serial interface clk_p output differential mipi (sub ? lvds) serial clock/strobe (positive) clk_n output differential mipi (sub ? lvds) serial clock/strobe (negative) line_valid output line_valid (lv) output. qualified by pixclk frame_valid output frame_valid (fv) output. qualified by pixclk d out [9:0] output parallel pixel data output. qualified by pixclk pixclk output pixel clock. used to qualify the lv, fv, and d out [9:0] outputs flash output flash output. synchronization pulse for external light source. can be left floating if not used v pp supply power supply used to program one-time programmable (otp) memory v dd_ tx supply digital phy power supply. digital power supply for the serial interface v aa supply analog power supply v aa _pix supply analog power supply for the pixel array a gnd supply analog ground v dd supply digital core power supply v dd_ io supply i/o power supply d gnd supply common ground for digital and i/o v dd_ pll supply pll power supply
ar0542 www. onsemi.com 8 output data format parallel pixel data interface ar0542 image data is read out in a progressive scan. v alid image data is surrounded by horizontal blanking and vertical blanking, as shown in figure 5. the amount of horizontal blanking and vertical blanking is programmable; lv is high during the shaded region of the figure. fv timing is described in the ?output data timing (parallel pixel data interface)?. figure 5. spatial illustration of image readout ..................................... ..................................... 00 00 00 .................. 00 00 00 00 00 00 .................. 00 00 00 ................................. ................................. 00 00 00 .................. 00 00 00 00 00 00 .................. 00 00 00 valid image horizontal blanking 00 00 00 .................. 00 00 00 00 00 00 .................. 00 00 00 00 00 00 .................. 00 00 00 00 00 00 .................. 00 00 00 00 00 00 ..................................... 00 00 00 00 00 00 ..................................... 00 00 00 00 00 00 ..................................... 00 00 00 00 00 00 ..................................... 00 00 00 vertical blanking vertical/horizontal blanking p 0,0 p 0,1 p 0,2 p 1,0 p 1,1 p 1,2 p 0,n ? 1 p 0,n p 1,n ? 1 p 1,n p m ? 1,0 p m ? 1,1 p m,0 p m,1 p m ? 1,n ? 1 p m ? 1,n p m,n ? 1 p m,n output data timing (parallel pixel data interface) ar0542 output data is synchronized with the pixclk output. when lv is high, one pixel value is output on the 10 ? bit d out output every pixclk period. the pixel clock frequency can be determined based on the sensor?s master input clock and internal pll configuration. the rising edges on the pixclk signal occurs one ? half of a pixel clock period after transitions on lv, fv, and d out ( see figure 6). this allows pixclk to be used as a clock to sample the data. pixclk is continuously enabled, even during the blanking period. the ar0542 can be programmed to delay the pixclk edge relative to the d out transitions. this can be achieved by programming the corresponding bits in the row_speed register. the parameters p, a, and q in figure 7 are defined in table 4. figure 6. pixel data timing example p 0 [9:0] p 1 p 2 p 3 p 4 p 5n ? 2 p n ? 1 p n valid image data blanking blanking lv pixclk d out [11:0] p [9:0] [9:0] [9:0] [9:0] [9:0] [9:0]
ar0542 www. onsemi.com 9 figure 7. row timing and fv/lv signals fv lv number of master clocks paq aqap table 4. row timing parameter name equation default timing pixclk_period pixel clock period r0x3016?7[2:0] / vt_pix_clk_freq_mhz 1 pixel clock = 11.9 ns s skip (subsampling) factor for x_odd_inc = y_odd_inc = 3, s = 2. for x_odd_inc = y_odd_inc = 7, s = 4. otherwise, s = 1 1 a active data time (x_addr_end ? x_addr_start + x_odd_inc) * op_pix ? clk_period/s 30.85 s p frame start/end blanking 6 * pixclk_period 6 pixel clocks = 71.4 ns q horizontal blanking (line_length_pck * pixclk_period ? a) 11.5 s a + q row time line_length_pck * pixclk_period 42.4 s n number of rows (y_addr_end ? y_addr_start + y_odd_inc)/s 1944 rows v vertical blanking ((frame_length_lines ? n) * (a+q)) + q ? (2*p) 3.27 ms t frame valid time (n * (a + q)) ? q + (2*p) 82.33 ms f total frame time line_length_pck * frame_length_lines * pixclk_period 85.60 ms the sensor timing (table 4) is shown in terms of pixel clock and master clock cycles (see figure 6). the settings in table 4 or the on-chip pll generate an 84 mhz output pixel clock (op_pix_clk) given a 24-mhz input clock to the ar0542. equations for calculating the frame rate are given in ?frame rate control?.
ar0542 www. onsemi.com 10 two-wire serial register interface the two-wire serial interface bus enables read/write access to control and status registers within the ar0542. this interface is designed to be compatible with the electrical characteristics and transfer protocols of the two-wire serial register interface specification. the interface protocol uses a master/slave model in which a master controls one or more slave devices. the sensor acts as a slave device. the master generates a clock (s clk ) that is an input to the sensor and is used to synchronize transfers. data is transferred between the master and the slave on a bidirectional signal (s data ). s data is pulled up to v dd_ io off-chip by a 1.5 k resistor. either the slave or master device can drive s data low?the interface protocol determines which device is allowed to drive s data at any given time. the protocols described in the two-wire serial interface specification allow the slave device to drive s clk low; the ar0542 uses s clk as an input only and therefore never drives it low. protocol data transfers on the two-wire serial interface bus are performed by a sequence of low-level protocol elements: 1. a (repeated) start condition 2. a slave address/data direction byte 3. an (a no) acknowledge bit 4. a message byte 5. a stop condition the bus is idle when both s clk and s data are high. control of the bus is initiated with a start condition, and the bus is released with a stop condition. only the master can generate the start and stop conditions. start condition a start condition is defined as a high-to-low transition on s data while s clk is high. at the end of a transfer, the master can generate a start condition without previously generating a stop condition; this is known as a ?repeated start? or ?restart? condition. stop condition a stop condition is def ined as a low -to-high transition on s data while s clk is high. data transfer data is transferred serially, 8 bits at a time, with the msb transmitted first. each byte of data is followed by an acknowledge bit or a no-acknowledge bit. this data transfer mechanism is used for the slave address/data direction byte and for message bytes. one data bit is transferred during each s clk clock period. s data can change when s clk is low and must be stable while s clk is high. slave address/data direction byte bits [7:1] of this byte represent the device slave address and bit [0] indicates the data transfer direction. a ?0? in bit [0] indicates a write, and a ?1? indicates a read. the default slave addresses used by the ar0542 for the mipi configured sensor are 0x6c (write address) and 0x6d (read address) in accordance with the mipi specification. alternate slave addresses of 0x6e (write address) and 0x6f (read address) can be selected by enabling and asserting the s addr signal through the gpi pad. an alternate slave address can also be programmed through r0x31fc. message byte message bytes are used for sending register addresses and register write data to the slave device and for retrieving register read data. acknowledge bit each 8-bit data transfer is followed by an acknowledge bit or a no-acknowledge bit in the s clk clock period following the data transfer. the transmitter (which is the master when writing, or the slave when reading) releases s data . the receiver indicates an acknowledge bit by driving s data low. as for data transfers, s data can change when s clk is low and must be stable while s clk is high. no-acknowledge bit the no-acknowledge bit is generated when the receiver does not drive s data low during the s clk clock period following a data transfer. a no-acknowledge bit is used to terminate a read sequence. typical sequence a typical read or write sequence begins by the master generating a start condition on the bus. after the start condition, the master sends the 8-bit slave address/data direction byte. the last bit indicates whether the request is for a read or a write, where a ?0? indicates a write and a ?1? indicates a read. if the address matches the address of the slave device, the slave device acknowledges receipt of the address by generating an acknowledge bit on the bus. if the request was a write, the master then transfers the 16-bit register address to which the write should take place. this transfer takes place as two 8-bit sequences and the slave sends an acknowledge bit after each sequence to indicate that the byte has been received. the master then transfers the data as an 8-bit sequence; the slave sends an acknowledge bit at the end of the sequence. the master stops writing by generating a (re)start or stop condition. if the request was a read, the master sends the 8-bit write slave address/data direction byte and 16-bit register address, the same way as with a write request. the master then generates a (re)start condition and the 8-bit read slave address/data direction byte, and clocks out the register data, eight bits at a time. the master generates an acknowledge bit after each 8-bit transfer. the slave?s internal register address
ar0542 www. onsemi.com 11 is automatically incremented after every 8 bits are transferred. the data transfer is stopped when the master sends a no-acknowledge bit. single read from random location this sequence (figure 8) starts with a dummy write to the 16-bit address that is to be used for the read. the master terminates the write by generating a restart condition. the master then sends the 8-bit read slave address/data direction byte and clocks out one byte of register data. the master terminates the read by generating a no-acknowledge bit followed by a stop condition. figure 8 shows how the internal register address maintained by the ar0542 is loaded and incremented as the sequence proceeds. figure 8. single read from random location previous reg address, n reg address, m m+1 s0 1 p a sr slave address reg address[15:8] reg address[7:0] slave address s = start condition p = stop condition sr = restart condition a = acknowledge a = no-acknowledge slave to master master to slave a a a a read data single read from current location this sequence (figure 9) performs a read using the current value of the ar0542 internal register address. the master terminates the read by generating a no-acknowledge bit followed by a stop condition. the figure shows two independent read sequences. figure 9. single read from current location previous reg address, n reg address, n+1 n+2 s1 slave address a s1 p slave address aa read data p a read data sequential read, start from random location this sequence (figure 10) starts in the same way as the single read from random location (figure 8). instead of generating a no-acknowledge bit after the first byte of data has been transferred, the master generates an acknowledge bit and continues to perform byte reads until ?l? bytes have been read. figure 10. sequential read, start from random location previous reg address, n reg address, m s0 slave address a a reg address[15:8] p a m+1 a a a 1 sr reg address[7:0] read data slave address m+l m+l ? 1 m+l ? 2 m+1 m+2 m+3 a read data a read data a read data read data sequential read, start from current location this sequence (figure 11) starts in the same way as the single read from current location (figure 9). instead of generating a no-acknowledge bit after the first byte of data has been transferred, the master generates an acknowledge bit and continues to perform byte reads until ?l? bytes have been read.
ar0542 www. onsemi.com 12 figure 11. sequential read, start from current location n+l n+l ? 1 n+2 n+1 previous reg address, n p a s 1 read data a slave address read data read data read data aaa single write to random location this sequence (figure 12) begins with the master generating a start condition. the slave address/data direction byte signals a write and is followed by the high then low bytes of the register address that is to be written. the master follows this with the byte of write data. the write is terminated by the master generating a stop condition. figure 12. single write to random location previous reg address, n reg address, m m+1 s0 p slave address reg address[15:8] reg address[7:0] a a a a a write data sequential write, start at random location this sequence (figure 13) starts in the same way as the single write to random location (figure 12). instead of generating a no-acknowledge bit after the first byte of data has been transferred, the master generates an acknowledge bit and continues to perform byte writes until ?l? bytes have been written. the write is terminated by the master generating a stop condition. figure 13. sequential write, start at random location previous reg address, n reg address, m m+1 s0 slave address a reg address[15:8] a a a reg address[7:0] m+l m+l ? 1 m+l ? 2 m+1 m+2 m+3 write data a a a p a write data write data a write data write data registers the ar0542 provides a 16-bit register address space accessed through a serial interface (?two-wire serial register interface?). see the ar0542 register reference for details.
ar0542 www. onsemi.com 13 programming restrictions table 6 shows a list of programming rules that must be adhered to for correct operation of the ar0542. it is recommended that these rules are encoded into the device driver stack-either implicitly or explicitly. table 5. definitions for programming rules name definition xskip xskip = 1 if x_odd_inc = 1; xskip = 2 if x_odd_inc = 3; xskip = 4 if x_odd_inc = 7 yskip yskip = 1 if y_odd_inc = 1; yskip = 2 if y_odd_inc = 3; yskip = 4 if y_odd_inc = 7 table 6. programming rules parameter minimum value maximum value coarse_integration_time 4 (8 is recommended) frame_length_lines ? coarse_integration_time_max _margin fine_integration_time fine_integration_time_min line_length_pck ? fine_integration_time_max_m argin digital_gain_* digital_gain_* is an integer multiple of digital_gain_step_size digital_gain_min digital_gain_max frame_length_lines min_frame_length_lines max_frame_length_lines line_length_pck min_line_length_pck max_line_length_pck ((x_addr_end ? x_addr_start + x_odd_inc)/xskip) + min_line_blanking_pck frame_length_lines ((y_addr_end ? y_addr_start + y_odd_inc)/yskip) + min_frame_blanking_lines x_addr_start (must be an even number) x_addr_min x_addr_max x_addr_end (must be an odd number) x_addr_start x_addr_max (x_addr_end ? x_addr_start + x_odd_inc) must be positive must be positive y_addr_start (must be an even number) y_addr_min y_addr_max y_addr_end (must be an odd number) y_addr_start y_addr_max (y_addr_end ? y_addr_start + y_odd_inc) must be positive must be positive x_even_inc (must be an even number) min_even_inc max_even_inc y_even_inc (must be an even number) min_even_inc max_even_inc x_odd_inc (must be an odd number) min_odd_inc max_odd_inc y_odd_inc (must be an odd number) min_odd_inc max_odd_inc scale_m scaler_m_min scaler_m_max scale_n scaler_n_min scaler_n_max x_output_size (must be even number ? this is enforced in hardware) 256 2608
ar0542 www. onsemi.com 14 table 6. programming rules (continued) parameter maximum value minimum value y_output_size (must be even number ? this is enforced in hardware) 2 frame_length_lines with subsampling, start and end pixels must be addressed (impact on x/y start/end addresses, function of image orientation bits) output size restrictions when the parallel pixel data path is in use, the only restriction on x_output_size is that it must be even (x_output_size[0] = 0), and this restriction is enforced in hardware. when the serial pixel data path is in use, there is an additional restriction that x_output_size must be small enough such that the output row time (set by x_output_size, the framing and crc overhead of 12 bytes and the output clock rate) must be less than the row time of the video array (set by line_length_pck and the video timing clock rate). effect of scaler on legal range of output sizes when the scaler is enabled, it is necessary to adjust the values of x_output_size and y_output_size to match the image size generated by the scaler. the ar0542 will operate incorrectly if the x_output_size and y_output_size are significantly larger than the output image. to understand the reason for this, consider the situation where the sensor is operating at full resolution and the scaler is enabled with a scaling factor of 32 (half the number of pixels in each direction). this situation is shown in figure 14. figure 14. effect of limiter on the data path core output: full resolution, x_output_size = x_addr_end ? x_addr_start + 1 line_valid scaler output: scaled to half size line_valid pixel_valid limiter output: scaled to half size, x_output_size = x_addr_end ? x_addr_start + 1 line_valid pixel_valid pixel_valid in figure 14, three different stages in the data path (see ?digital data path?) are shown. the first stage is the output of the sensor core. the core is running at full resolution and x_output_size is set to match the active array size. the line_valid signal is asserted once per row and remains asserted for n pixel times. the pixel_valid signal toggles with the same timing as line_valid, indicating that all pixels in the row are valid. the second stage is the output of the scaler, when the scaler is set to reduce the image size by one-half in each dimension. the effect of the scaler is to combine groups of pixels. therefore, the row time remains the same, but only half the pixels out of the scaler are valid. this is signaled by transitions in pixel_valid. overall, pixel_valid is asserted for ( n /2) pixel times per row. the third stage is the output of the limiter when the x_output_size is still set to match the active array size. because the scaler has reduced the amount of valid pixel data without reducing the row time, the limiter attempts to pad the row with ( n /2) additional pixels. if this has the ef fect of extending lv across the whole of the horizontal blanking time, the ar0542 will cease to generate output frames. a correct configuration is shown in figure 15, in addition to showing the x_output_size reduced to match the output size of the scaler. in this configuration, the output of the limiter does not extend lv. figure 15 also shows the effect of the output fifo, which forms the final stage in the data path. the output fifo merges the intermittent pixel data back into a contiguous stream. although not shown in this example, the output fifo is also capable of operating with an output clock that is at a different frequency from its input clock.
ar0542 www. onsemi.com 15 figure 15. timing of data path core output: full resolution, x_output_size = x_addr_end ? x_addr_start + 1 line_valid scaler output: scaled to half size line_valid pixel_valid limiter output: scaled to half size, x_output_size = (x_addr_end ? x_addr_start + 1)/2 pixel_valid line_valid pixel_valid output fifo: scaled to half size, x_output_size = (x_addr_end ? x_addr_start + 1)/2 line_valid pixel_valid output data timing the output fifo acts as a boundary between two clock domains. data is written to the fifo in the vt (video timing) clock domain. data is read out of the fifo in the op (output) clock domain. when the scaler is disabled, the data rate in the vt clock domain is constant and uniform during the active period of each pixel array row readout. when the scaler is enabled, the data rate in the vt clock domain becomes intermittent, corresponding to the data reduction performed by the scaler. a key constraint when configuring the clock for the output fifo is that the frame rate out of the fifo must exactly match the frame rate into the fifo. when the scaler is disabled, this constraint can be met by imposing the rule that the row time on the serial data stream must be greater than or equal to the row time at the pixel array. the row time on the serial data stream is calculated from the x_output_size and the data_format (8 or 10 bits per pixel), and must include the time taken in the serial data stream for start of frame/row, end of row/frame and checksum symbols. caution: if this constraint is not met, the fifo will either underrun or overrun. fifo underrun or overrun is a fatal error condition that is signaled through the data path_status register (r0x306a). changing registers while streaming the following registers should only be reprogrammed while the sensor is in software standby: ? ccp_channel_identifier ? ccp_data_format ? ccp_signaling_mode ? vt_pix_clk_div ? vt_sys_clk_div ? pre_pll_clk_div ? pll_multiplier ? op_pix_clk_div ? op_sys_clk_div ? scale_m programming restrictions when using global reset interactions between the registers that control the global reset imposes some programming restrictions on the way in which they are used; these are discussed in ?analog gain?.
ar0542 www. onsemi.com 16 control of the signal interface this section describes the operation of the signal interface in all functional modes. serial register interface the serial register interface uses these signals: ? s clk ? s data ? s addr ( through the gpi pad ) s clk is an input-only signal and must always be driven to a valid logic level for correct operation; if the driving device can place this signal in high-z, an external pull-up resistor should be connected on this signal. s data is a bidirectional signal. an external pull-up resistor should be connected on this signal. s addr is a signal, which can be optionally enabled and controlled by a gpi pad, to select an alternate slave address. these slave addresses can also be programmed through r0x31fc. this interface is described in detail in ?two-wire serial register interface?. default power-up state the ar0542 sensor can provide two separate interfaces for pixel data: the mipi serial interface and a parallel data interface. at powerup and after a hard or soft reset, the reset state of the sensor is to enable serial interface when available. the serial pixel data interface uses the following output-only signal pairs: ? data0_p ? data0_n ? clk_p ? clk_n the signal pairs are driven differentially using sub-lvds switching levels. the serial pixel data interface is enabled by default at power up and after reset. the data0_p, data0_n, clk_p, and clk_n pads are turned off if the smia serial disable bit is asserted (r0x301a-b[12]=1) or when the sensor is in the soft standby state. in data/clock mode the clock remains high when no data is being transmitted. in data/ strobe mode before frame start, clock is low and data is high. when the serial pixel data interface is used, the line_valid, frame_valid, pixclk and d out [9:0] signals (if present) can be left unconnected. mipi serial pixel data interface the serial pixel data interface uses the following output-only signal pairs: ? data0_p ? data0_n ? data1_p ? data1_n ? clk_p ? clk_n the signal pairs use both single-ended and differential signaling, in accordance with the mipi specification. the serial pixel data interface is enabled by default at power up and after reset. the data0_p, data0_n, data1_p, data1_n, clk_p and clk_n pads are set to the ultra low power state (ulps) if the smia serial disable bit is asserted (r0x301a-b[12]=1) or when the sensor is in the hardware standby or soft standby system states. when the serial pixel data interface is used, the line_valid, frame_valid, pixclk and d out [9:0] signals (if present) can be left unconnected. the ccp_data_format (r0x0112-3) register can be programmed to any of the following data format settings that are supported: ? 0x0a0a ? sensor supports raw10 uncompressed data format. this mode is supported by discarding all but the upper 10 bits of a pixel value. ? 0x0808 ? sensor supports raw8 uncompressed data format. this mode is supported by discarding all but the upper 8 bits of a pixel value. ? 0x0a08 ? sensor supports raw8 data format in which an adaptive compression algorithm is used to perform 10-bit to 8-bit compression on the upper 10 bits of each pixel value the serial_format register (r0x31ae) register controls which serial interface is in use when the serial interface is enabled (reset_register[12] = 0). the following serial formats are supported: ? 0x0201 ? sensor supports single-lane mipi operation ? 0x0202 ? sensor supports dual-lane mipi operation parallel pixel data interface the parallel pixel data interface uses these output-only signals: ? fv ? lv ? pixclk ? d out [9:0] the parallel pixel data interface is disabled by default at power up and after reset. it can be enabled by programming r0x301a. table 8 shows the recommended settings. when the parallel pixel data interface is in use, the serial data output signals (data0_p, data0_n, data1_p, data1_n, clk_p, and clk_n) can be left unconnected.
ar0542 www. onsemi.com 17 set reset_register[12] to disable the serializer while in parallel output mode. to use the parallel interface, the v dd _tx pad must be tied to a 1.8 v supply. for mipi sensor, the vdd_io supply can be set at 1.8 v or 2.8 v (nominal). output enable control when the parallel pixel data interface is enabled, its signals can be switched asynchronously between the driven and high-z under pin or register control, as shown in table 7. selection of a pin to use for the oe_n function is described in ?general purpose inputs?. table 7. output enable control oe_n pin drive signals r0x301a?b[6] description disabled 0 interface high-z disabled 1 interface driven 1 0 interface high-z x 1 interface driven 0 x interface driven configuration of the pixel data interface fields in r0x301a are used to configure the operation of the pixel data interface. the supported combinations are shown in table 8. table 8. configuration of the pixel data interface serializer disable r0x301 a?b[12] parallel enable r0x301a?b[7] standby end-of-frame r0x301a?b[4] description 0 0 1 power up default serial pixel data interface and its clocks are enabled. transitions to soft standby are synchronized to the end of frames on the serial pixel data interface 1 1 0 parallel pixel data interface, sensor core data output. serial pixel data interface and its clocks disabled to save power. transitions to soft standby are synchronized to the end of the current row readout on the parallel pixel data interface 1 1 1 parallel pixel data interface, sensor core data output. serial pixel data interface and its clocks disabled to save power. transitions to soft standby are synchronized to the end of frames in the parallel pixel data interface
ar0542 www. onsemi.com 18 system states the system states of the ar0542 are represented as a state diagram in figure 16 and described in subsequent sections. the effect of reset_bar on the system state and the configuration of the pll in the different states are shown in table 9. the sensor?s operation is broken down into three separate states: hardware standby, software standby, and streaming. the transition between these states might take a certain amount of clock cycles as outlined in table 9. figure 16. ar0542 system states powered off streaming initialization timeout two-wire serial interface write mode_select = 0 pll lock pll locked software reset initiated (synchronous from any state) wait for frame end software standby two-wire serial interface write mode_select = 1 two-wire serial interface write software_reset = 1 hardware standby 2400 extclk cycles reset_bar = 0 or por = 0 reset_bar = 1 or xshutdown = 1 pll not locked on sensor) frame in progress reset _bar or xshutdown transitions 1 ? > 0 (asynchronous from any state ) power supplies turned off (asychronous from any state) (only if por is por active initialization internal xshutdown = 0 powerd on por = 1 table 9. xshutdown and pll in system states state xshutdown pll powered off x vco powered down por active x hardware standby 0 internal initialization 1 software standby pll lock vco powering up and locking, pll output bypassed streaming vco running, pll output active wait for frame end
ar0542 www. onsemi.com 19 power-on reset sequence when power is applied to the ar0542, it enters a low-power hardware standby state. exit from this state is controlled by the later of two events: ? the negation of the xshutdown input. ? a timeout of the internal power-on reset circuit. when xshutdown is asserted it asynchronously resets the sensor, truncating any frame that is in progress. while xshutdown is asserted (or the internal power-on reset circuit is active) the ar0542 is in its lowest-powered, powered-up state; the internal pll is disabled, the serializer is disabled and internal clocks are gated off. when the sensor leaves the hardware standby state it performs an internal initialization sequence that takes 2400 extclk cycles. after this, it enters a low-power software standby state. while the initialization sequence is in progress, the ar0542 will not respond to read transactions on its two-wire serial interface. therefore, a method to determine when the initialization sequence has completed is to poll a sensor register; for example, r0x0000. while the initialization sequence is in progress, the sensor will not respond to its device address and reads from the sensor will result in a nack on the two-wire serial interface bus. when the sequence has completed, reads will return the operational value for the register (0x4800 if r0x0000 is read). when the sensor leaves software standby mode and enables the vco, an internal delay will keep the pll disconnected for up to 1ms so that the pll can lock. the vco lock time is 200 s (typical), 1ms (maximum). soft reset sequence the ar0542 can be reset under software control by writing ?1? to software_reset (r0x0103). a software reset asynchronously resets the sensor, truncating any frame that is in progress. the sensor starts the internal initialization sequence, while the pll and analog blocks are turned off. at this point, the behavior is exactly the same as for the power-on reset sequence. signal state during reset table 10 shows the state of the signal interface during hardware standby (reset_bar asserted) and the default state during software standby (after exit from hardware standby and before any registers within the sensor have been changed from their default power-up values). table 10. signal state during reset pad name pad type hardware standby software standby extclk input enabled. must be driven to a valid logic level xshutdown/reset_bar input enabled. must be driven to a valid logic level line_valid output high-z. can be left disconnected/floating frame_valid output d out[ 9:0] output pixclk output s clk input enabled. must be pulled up or driven to a valid logic level s data i/o enabled as an input. must be pulled up or driven to a valid logic level flash output high-z logic 0 data0_p output mipi: ultra low-power state (ulps), represented as an lp-00 state on the wire (both wires at 0 v) data0_n output data1_p output data1_n output clk_p output clk_n output gpi[3:0] input powered down. can be left disconnected/floating test input enabled. must be driven to a logic 1 for a serial mipi-configured sensor
ar0542 www. onsemi.com 20 general purpose inputs the ar0542 provides four general purpose inputs. after reset, the input pads associated with these signals are powered down by default, allowing the pads to be left disconnected/floating. the general purpose inputs are enabled by setting reset_register[8] (r0x301a). once enabled, all four inputs must be driven to valid logic levels by external signals. the state of the general purpose inputs can be read through gpi_status[3:0] (r0x3026). in addition, each of the following functions can be associated with none, one, or more of the general purpose inputs so that the function can be directly controlled by a hardware input: ? output enable (see ?output enable control?) ? trigger (see the sections below) ? standby functions ? s addr selection (see ?serial register interface?) the gpi_status register is used to associate a function with a general purpose input. streaming/standby control the ar0542 can be switched between its soft standby and streaming states under pin or register control, as shown in table 11. selection of a pin to use for the standby function is described in ? general purpose inputs?. the state diagram for transitions between soft standby and streaming states is shown in figure 16. table 11. streaming/standby standby streaming r0x301a?b[2] description disabled 0 soft standby disabled 1 streaming x 0 soft standby 0 1 streaming 1 x soft standby clocking the ar0542 contains a pll for timing generation and control. the pll contains a prescaler to divide the input clock applied on extclk, a vco to multiply the prescaler output, and a set of dividers to generate the output clocks. both smia profile 0 and profile 1/2 clock schemes are supported. sensor profile level represents an increasing level of data rate reduction for video applications, for example, viewfinder in full resolution. the clocking scheme can be selected by setting r0x306e?f[7] to 0 for profile 0 or to 1 for profile 1/2. figure 17. ar0542 profile 1/2 clocking structure extclk (m) external input clock ext_clk_freq_mhz clk_pixel vt_pix_clk vt_sys_clk op_sys_clk op_pix_clk clk_op pre_pll_clk_div 2 (1 ? 64) pll_multiplier 70 (even values : 32 ? 384) (odd values : 17 ? 191) op_pix_clk_div 10 (8, 10) op pix clk divider row_speed [10:8] 1 (1, 2, 4) clk_op divider vt pix clk divider op sys clk divider vt sys clk divider pll multiplier pre pll divider pll input clock pll_ip_clk_freq (4 ? 24 mhz) pll internal vco frequency (384 ? 840 mhz) clk_pixel divider vt_pix_clk_div 5(4 ? 16) row_speed [2:0] 1 (1, 2, 4) (6 ? 27 mhz) (1 must only be used with even pll_ multiplier values) op_sys_clk_div 1(1, 2, 4, 6, 8, 10, 12, 14, 16) vt_sys_clk_div 1(1, 2, 4, 6, 8, 10, 12, 14, 16) pll figure 17 shows the different clocks and the names of the registers that contain or are used to control their values. also shown is the default setting for each divider/multipler
ar0542 www. onsemi.com 21 control register and the range of legal values for each divider/multiplier control register. the parameter limit register space contains registers that declare the minimum and maximum allowable values for: ? the frequency allowable on each clock ? the divisors that are used to control each clock these factors determine what are valid values, or combinations of valid values, for the divider/multiplier control registers: ? the minimum/maximum frequency limits for the associated clock must be met pll_ip_clk_freq must be in the range 4?24 mhz. higher frequencies are preferred. pll internal vco frequency must be in the range 384?840 mhz. ? the minimum/maximum value for the divider/multiplier must be met. range for m: 17 ?384. (in addition odd values between 17?191 and even values between 32?384 are accepted.) range for n: 0 ? 63. range for (n+1): 1?64. ? clk_op must never run faster than the clk_pixel to ensure that the output data stream is contiguous. ? given the maximum programmed line length, the minimum blanking time, the maximum image width, the available pll divisor/multiplier values, and the requirement that the output line time (including the necessary blanking) must be output in a time equal to or less than the time defined by line_length_pck. although the pll vco input frequency range is advertised as 4?24 mhz, superior performance is obtained by keeping the vco input frequency as high as possible. the usage of the output clocks is shown below: ? clk_pixel (vt_pix_clk / row_speed[2:0]) is used by the sensor core to readout and control the timing of the pixel array. the sensor core produces one 10-bit pixel each vt_pix_clk period. the line length (line_length_pck) and fine integration time (fine_integration_time) are controlled in increments of the vt_pix_clk period. ? clk_op (op_pix_clk / row_speed[10:8]) is used to load parallel pixel data from the output fifo (see figure 35 on page 40) to the serializer. the output fifo generates one pixel each op_pix_clk period. the pixel is either 8-bit or 10-bit, depending upon the output data format, controlled by r0x0112?3 (ccpdata_format). ? op_sys_clk is used to generate the serial data stream on the output. the relationship between this clock frequency and the op_pix_clk frequency is dependent upon the output data format. in profile 1/2, the output clock frequencies can be calculated as: clk_pix_freq_mhz ext_clk_freq_mhz pll_multiplier clk_pixel_divn pre_pll_clk_div vt_sys_clk_div vt_pix_clk_div row_speed[2 : 0] (eq. 1) clk_op_freq_mhz ext_clk_freq_mhz pll_multiplier pre_pll_clk_div op_sys_clk_div op_pix_clk_div row_speed[10 : 8] (eq. 2) op_sys_clk_freq_mhz ext_clk_freq_mhz pll_multiplier pre_pll_clk_div op_sys_clk_div (eq. 3) note: for dual-lane mipi interface, clk_pixel_divn = 1. for other interfaces (parallel and single-lane mipi), clk_pixel_divn = 2. in profile 0, raw10 data format is required. as a result, op_pix_clk_div should be set to 10. also, due to the inherent design of the ar0542 sensor, vt_pix_clk_div should be set to 5 for profile 0 mode. pll clocking the pll divisors should be programmed while the ar0542 is in the software standby state. after programming the divisors, it is necessary to wait for the vco lock time before enabling the pll. the pll is enabled by entering the streaming state. an external timer will need to delay the entrance of the streaming mode by 1 millisecond so that the pll can lock. the effect of programming the pll divisors while the ar0542 is in the streaming state is undefined. influence of ccp_data_format r0x0112?3 (ccp_data_format) controls whether the pixel data interface will generate 10 or 8 bits per pixel. when the pixel data interface is generating 8 bits per-pixel, op_pix_clk_div must be programmed with the value 8. when the pixel data interface is generating 10 bits per pixel, op_pix_clk_div must be programmed with the value 10. influence of ccp2_signalling_mode r0x0111 (ccp2_signalling_mode) controls whether the serial pixel data interface uses data/strobe signaling or data/clock signaling. when data/clock signaling is selected, the pll_multiplier supports both odd and even values. when data/strobe signaling is selected, the pll_multiplier only supports even values; the least significant bit of the programmed value is ignored and treated as ?0.? this behavior is a result of the implementation of the ccp serializer and the pll. when the serializer is using data and strobe signaling, it uses both edges of the op_sys_clk, and therefore that clock runs at one half of the bit rate. all of the programmed divisors are set up to make this behavior invisible. for example, when the divisors are programmed
ar0542 www. onsemi.com 22 to generate a pll output of 640 mhz, the actual pll output is 320 mhz, but both edges are used. when the serializer is using data and clock signaling, it uses a single edge on the op_sys_clk, and therefore that clock runs at the bit rate. to disguise this behavior from the programmer, the actual pll multiplier is right-shifted by one bit relative to the programmed value when ccp2_signalling_mode selects data/strobe signaling. clock control the ar0542 uses an aggressive clock-gating methodology to reduce power consumption. the clocked logic is divided into a number of separate domains, each of which is only clocked when required. when the ar0542 enters a low-power state, almost all of the internal clocks are stopped. the only exception is that a small amount of logic is clocked so that the two-wire serial interface continues to respond to read and write requests. features shading correction (sc) lenses tend to produce images whose brightness is significantly attenuated near the edges. there are also other factors causing fixed pattern signal gradients in images captured by image sensors. the cumulative result of all these factors is known as image shading. the ar0542 has an embedded shading correction module that can be programmed to counter the shading effects on each individual red, greenb, greenr, and blue color signal. the correction function color-dependent solutions are calibrated using the sensor, lens system and an image of an evenly illuminated, featureless gray calibration field. from the resulting image, register values for the color correction function (coefficients) can be derived. the correction functions can then be applied to each pixel value to equalize the response across the image as follows: pcorrected(row, col) psensor(row, col) f(row, col) (eq. 4) where p are the pixel values and f is the color dependent correction functions for each color channel. each function includes a set of color-dependent coefficients defined by registers r0x3600?3726. the function?s origin is the center point of the function used in the calculation of the coefficients. using an origin near the central point of symmetry of the sensor response provides the best results. the center point of the function is determined by origin_c (r0x3782) and origin_r (r0x3784) and can be used to counter an offset in the system lens from the center of the sensor array. one-time programmable memory (otpm) the ar0542 features 7.7 kb of one-time programmable memory (otpm) for storing shading correction coefficients, individual module id, and sensor specific information. it takes roughly 5 kb (102 registers x 16-bits x 3 sets = 4896 bits) to store three sets of illumination-dependent shading coefficients. the otpm array has a total of 201 accessible row-addresses, with each row having two 20-bit words per row. in each word, 16 bits are used for data storage, while the remaining 4 bits are used by the error detection and correction scheme. otp memory can be accessed through two-wire serial interface. the ar0542 uses the auto mode for fast otpm programming and read operations. during the programming process, a dedicated high voltage pin (v pp ) needs to be supplied with a 6.5 v +3% voltage to perform the anti-fusing operation, and a slew rate of 1 v/ s or slower is recommended for v pp supply. instantaneous v pp cannot exceed 9 v at any time. the completion of the programming process will be communicated by a register through the two-wire serial interface. because this programming pin needs to sustain a higher voltage than other input/output pins, having a dedicated high voltage pin (v pp ) minimizes the design risk. if the module manufacturing process can probe the sensor at the die or pcb level (that is, supply all the power rails, clocks, and two-wire serial interface signals), then this dedicated high voltage pin does not need to be assigned to the module connector pinout. however, if the v pp pin needs to be bonded out as a pin on the module, the trace for v pp needs to carry a maximum of 1 ma ? for programming only. this pin should be left floating once the module is integrated to a design. if the v pp pin does not need to be bonded-out as a pin on the module, it should be left floating inside the module. the programming of the otpm requires the sensor to be fully powered and remain in software standby with its clock input applied. the information will be programmed through the use of the two-wire serial interface, and once the data is written to an internal register, the programming host machine will apply a high voltage to the programming pin, and send a program command to initiate the anti-fusing process. after the sensor has finished programming the otpm, a status bit will be set to indicate the end of the programming cycle, and the host machine can poll the setting of the status bit through the two-wire serial interface. only one programming cycle for the 16-bit word can be performed. reading the otpm data requires the sensor to be fully powered and operational with its clock input applied. the data can be read through a register from the two-wire serial interface. programming the otpm program the ar0542 otpm as follows: 1. apply power to all the power rails of the sensor (v dd _io, v aa , v aa _pix, and digital 1.8 v).
ar0542 www. onsemi.com 23 ? on semiconductor recommends setting v aa to 3.1 v during the programming process. all other supplies must be at their nominal voltage. ? ensure that the v pp pin is floating during sensor power-up. 2. provide an extclk clock input (12 mhz is recommended). 3. set r0x301a = 0x10d8, to put sensor in the soft standby mode. 4. set r0x3064[9] =1 to bypass pll. 5. set r0x3054[8]=1 6. write data (102 words for one set of lsc coefficients) into the otpm data registers (r0x3800?r0x38ca for one set of lsc coefficients). 7. set otpm start address register r0x3050[15:8] = 0 to program the array with the first batch of data. note: when programming the second batch of data, set the start address to 128 (considering that all the previous 0?127 locations are already written to by the data registers 0?255), otherwise the start address should be set accordingly. 8. set r0x3054[9] = 0 to ensure that the error checking and correction is enabled. 9. set the length register (r0x304c [7:0]) accordingly, depending on the number of otm data registers that are filled in (0x66 for 102 words). it may take about 500 ms for one set of lsc (102 words). 10. set r0x3052 = 0x2504 (otpm_config) 11. ramp up v pp to 6.5 v. the recommended slew rate for v pp is 1 v/ s or slower. 12. set the otpm_control_auto_wr_start bit in the otpm_manual_control register r0x304a[0] = 1, to initiate the auto program sequence. the sensor will now program the data into the otpm starting with the location specified by the start address. 13. poll otpm_control_auto_wr_end (r0x304a [1]) to determine when the sensor is finished programming the word. 14. repeat steps 13 and 14. 15. remove the high voltage (v pp ) and float the v pp pin. reading the otpm read the ar0542 otpm as follows: 1. perform the proper reset sequence to the sensor by setting r0x0103 = 1. 2. set otpm_config register r0x3052 = 0x2704. 3. set r0x3054[8] = 1. 4. program r0x3050[15:8] with the appropriate value to specify the start address (0x0 for address 0). 5. program r0x304c [7:0] with the appropriate value to specify the length (number of data registers to be read back, starting from the specified start address ? 0x66 for 102 words). 6. initiate the auto read sequence by setting the otpm_control_auto_read_start bit r0x304a[4] = 1. 7. poll the otpm_control_auto_rd_end bit (r0x304a[5]) to determine when the sensor is finished reading the word(s). data can now be read back from the otpm_data registers (r0x3800?r0x39fe). 8. verify that the read data from the otpm_data registers are the expected data. image acquisition mode the ar0542 supports the electronic rolling shutter (ers) mode. this is the normal mode of operation. when the ar0542 is streaming, it generates frames at a fixed rate, and each frame is integrated (exposed) using the ers. when the ers is in use, timing and control logic within the sensor sequences through the rows of the array, resetting and then reading each row in turn. in the time interval between resetting a row and subsequently reading that row, the pixels in the row integrate incident light. the integration (exposure) time is controlled by varying the time between row reset and row readout. for each row in a frame, the time between row reset and row readout is fixed, leading to a uniform integration time across the frame. when the integration time is changed (by using the two-wire serial interface to change register settings), the timing and control logic controls the transition from old to new integration time in such a way that the stream of output frames from the ar0542 switches cleanly from the old integration time to the new while only generating frames with uniform integration. see ?changes to integration time? in the ar0542 register reference. window control the sequencing of the pixel array is controlled by the x_addr_start, y_addr_start, x_addr_end, and y_addr_end registers. for both parallel and serial mipi interfaces, the output image size is controlled by the x_output_size and y_output_size registers. pixel border the default settings of the sensor provide a 2592 (h) x 1944 (v) image. a border of up to 8 pixels (4 in binning) on each edge can be enabled by reprogramming the x_addr_start, y_addr_start, x_addr_end, y_addr_end, x_output_size, and y_output_size registers accordingly. readout modes horizontal mirror when the horizontal_mirror bit is set in the image_orientation register, the order of pixel readout within
ar0542 www. onsemi.com 24 a row is reversed, so that readout starts from x_addr_end and ends at x_addr_start. figure 18 shows a sequence of 6 pixels being read out with horizontal_mirror = 0 and horizontal_mirror = 1. changing horizontal_mirror causes the bayer order of the output image to change; the new bayer order is reflected in the value of the pixel_order register. figure 18. effect of horizontal_mirror on readout order g0[9:0] r0[9:0] g1[9:0] r1[9:0] g2[9:0] r2[9:0] r2[9:0] g2[9:0] r1[9:0] g1[9:0] r0[9:0] g0[9:0] line_valid horizontal_mirror = 0 d out [9:0] horizontal_mirror = 1 d out [9:0] vertical flip when the vertical_flip bit is set in the image_orientation register, the order in which pixel rows are read out is reversed, so that row readout starts from y_addr_end and ends at y_addr_start. figure 19 shows a sequence of 6 rows being read out with vertical_flip = 0 and vertical_flip = 1. changing vertical_flip causes the bayer order of the output image to change; the new bayer order is reflected in the value of the pixel_order register. figure 19. effect of vertical_flip on readout order row0[9:0] row1[9:0] row2[9:0] row3[9:0] row4[9:0] row5[9:0] row5[9:0] row4[9:0] row3[9:0] row2[9:0] row0[9:0] frame_valid vertical_flip = 0 d out [9:0] vertical_flip = 0 d out [9:0] row1[9:0] subsampling the ar0542 supports subsampling. subsampling reduces the amount of data processed by the analog signal chain in the ar0542 thereby allowing the frame rate to be increased. subsampling is enabled by setting x_odd_inc and/or y_odd_inc. values of 1, 3, and 7 can be supported. setting both of these variables to 3 reduces the amount of row and column data processed and is equivalent to the 2 x 2 skipping readout mode provided by the ar0542. setting x_odd_inc = 3 and y_odd_inc = 3 results in a quarter reduction in output image size. figure 20 shows a sequence of 8 columns being read out with x_odd_inc = 3 and y_odd_inc = 1. figure 20. effect of x_odd_inc = 3 on readout sequence g0[9:0] r0[9:0] g1[9:0] r1[9:0] g2[9:0] r2[9:0] g3[9:0] r3[9:0] g0[9:0] r0[9:0] g2[9:0] r2[9:0] line_valid x_odd_inc = 1 d out [9:0] line_valid x_odd_inc = 3 d out [9:0] a 1/16 reduction in resolution is achieved by setting both x_odd_inc and y_odd_inc to 7. this is equivalent to 4 x 4 skipping readout mode provided by the ar0542. figure 21
ar0542 www. onsemi.com 25 shows a sequence of 16 columns being read out with x_odd_inc = 7 and y_odd_inc = 1. figure 21. effect of x_odd_inc = 7 on readout sequence g0[9:0] r0[9:0] g1[9:0] r1[9:0] g2[9:0] g7[9:0] r7[9:0] g0[9:0] r0[9:0] g4[9:0] r4[9:0] line_valid x_odd_inc = 1 d out [9:0] line_valid x_odd_inc = 7 d out [9:0] ... the effect of the different subsampling settings on the pixel array readout is shown in figure 22 through figure 24. figure 22. pixel readout (no subsampling) figure 23. pixel readout (x_odd_inc = 3, y_odd_inc = 3) x incrementing y incrementing x incrementing y incrementing figure 24. pixel readout (x_odd_inc = 7, y_odd_inc = 7) x incrementing y incrementing
ar0542 www. onsemi.com 26 programming restrictions when subsampling when subsampling is enabled as a viewfinder mode and the sensor is switched back and forth between full resolution and subsampling, on semiconductor recommends that line_length_pck be kept constant between the two modes. this allows the same integration times to be used in each mode. when subsampling is enabled, it may be necessary to adjust the x_addr_end, x_addr_star, y_addr_start, and y_addr_end settings: the values for these registers are required to correspond with rows/columns that form part of the subsampling sequence. the adjustment should be made in accordance with these rules: x_skip_factor = (x_odd_inc + 1) / 2 x_skip_factor = (x_odd_inc + 1) / 2 ? x_addr_start should be a multiple of x_skip_factor * 4 ? (x_addr_end ? x_addr_start + x_odd_inc) should be a multiple of x_skip_factor * 4 ? (y_addr_end ? y_addr_start + y_odd_inc) should be a multiple of y_skip_factor * 4 the number of columns/rows read out with subsampling can be found from the equation below: ? columns/rows = (addr_end ? addr_start + odd_inc) / skip_factor example: the sensor is set up to give out a full resolution 2592 x 1944 image: ? [full resolution starting address with (8,8)] reg = 0x0104, 1 //grouped_parameter_hold reg = 0x0382, 1 //x_odd_inc reg = 0x0386, 1 //y_odd_inc reg = 0x0344, 8 //x_addr_start reg = 0x0346, 8 //y_addr_start reg = 0x0348, 2599 //x_addr_end reg = 0x034a, 1951 //y_addr_end reg = 0x034c, 2592 //x_output_size reg = 0x034e, 1944 //y_output_size reg = 0x0104, 0 //grouped_parameter_hold to halve the resolution in each direction (1296 x 972), the registers need to be reprogrammed as follows: ? [2 x 2 skipping starting address with (8,8)] reg = 0x0104, 1 //grouped_parameter_hold reg = 0x0382, 3 //x_odd_inc reg = 0x0386, 3 //y_odd_inc reg = 0x0344, 8 //x_addr_start reg = 0x0346, 8 //y_addr_start reg = 0x0348, 2597 //x_addr_end reg = 0x034a, 1949 //y_addr_end reg = 0x034c, 1296 //x_output_size reg = 0x034e, 972 //y_output_size reg = 0x0104, 0 //grouped_parameter_hold to quarter the resolution in each direction (648 x 486), the registers need to be reprogrammed as follows: ? [4 x 4 skipping starting address with (8,8)] reg = 0x0104, 1 //grouped_parameter_hold reg = 0x0382, 7 //x_odd_inc reg = 0x0386, 7 //y_odd_inc reg = 0x0344, 8 //x_addr_start reg = 0x0346, 8 //y_addr_start reg = 0x0348, 2593 //x_addr_end reg = 0x034a, 1945 //y_addr_end reg = 0x034c, 648 //x_output_size reg = 0x034e, 486 //y_output_size reg = 0x0104, 0 //grouped_parameter_hold table 12 shows the row or column address sequencing for normal and subsampled readout. in the 2x skip case, there are two possible subsampling sequences (because the subsampling sequence only reads half of the pixels) depending upon the alignment of the start address. similarly, there will be four possible subsampling sequences in the 4x skip case (though only the first two are shown in table 12).
ar0542 www. onsemi.com 27 table 12. row address sequencing during subsampling odd_inc = 1?normal odd_inc = 3, 2x skip odd_inc = 7, 4x skip start = 0 start = 0 start = 0 0 0 0 1 1 1 2 3 4 4 5 5 6 7 8 8 8 9 9 9 10 11 12 12 13 13 14 15
ar0542 www. onsemi.com 28 binning the ar0542 supports 2 x 1 (column binning, also called x-binning) and 2 x 2 analog binning (row/column binning, also called xy-binning). binning has many of the same characteristics as subsampling, but because it gathers image data from all pixels in the active window (rather than a subset of them), it achieves superior image quality and avoids the aliasing artifacts that can be a characteristic side effect of subsampling. binning is enabled by selecting the appropriate subsampling settings (odd_inc = 3 and y_odd_inc = 1 for x ? binning, x_odd_inc = 3 and y_odd_inc = 3 for xy ? binning) and setting the appropriate binning bit in read_mode (r0x3040 ? 1). as with subsampling, x_addr_end and y_addr_end may require adjustment when binning is enabled. it is the first of the two columns/rows binned together that should be the end column/row in binning, so the requirements to the end address are exactly the same as in non ? binning subsampling mode. the effect of the different subsampling settings is shown in figure 25 and figure 26. binning can also be enabled when the 4x subsampling mode is enabled (x_odd_inc = 7 and y_odd_inc = 1 for x ? binning, x_odd_inc = 7 and y_odd_inc = 7 for xy ? binning). in this mode, however, not all pixels will be used so this is not a 4x binning implementation. an implementation providing a combination of skip2 and bin2 is used to achieve 4x subsampling with better image quality. the effect of this subsampling mode is shown in figure 27. figure 25. pixel readout (x_odd_inc = 3, y_odd_inc = 1, x_bin = 1) figure 26. pixel readout (x_odd_inc = 3, y_odd_inc = 3, xy_bin = 1) y incrementing x incrementing x incrementing y incrementing figure 27. pixel readout (x_odd_inc = 7, y_odd_inc = 7, xy_bin = 1) x incrementing y incrementing
ar0542 www. onsemi.com 29 binning address sequencing is a bit more complicated than during subsampling only, because of the implementation of the binning itself. for a given column n , there is only one other column, n_bin, that can be binned with, because of physical limitations in the column readout circuitry. the possible address sequences are shown in table 13. table 13. column address sequencing during binning odd_inc = 1?normal odd_inc = 3, 2x bin odd_inc = 7, 2x skip + 2x bin x_addr_start = 0 x_addr_start = 0 x_addr_start = 0 0 0/2 0/4 1 1/3 1/5 2 3 4 4/6 5 5/7 6 7 8 8/10 8/12 9 9/11 9/13 10 11 12 12/14 13 13/15 14 15 there are no physical limitations on what can be binned together in the row direction. a given row n will always be binned with row n+2 in 2x subsampling mode and with row n+4 in 4x subsampling mode. therefore, which rows get binned together depends upon the alignment of y_addr_start. the possible sequences are shown in t able 14. table 14. row address sequencing during binning odd_inc = 1?normal odd_inc = 3, 2x bin odd_inc = 7, 2x skip + 2x bin x_addr_start = 0 x_addr_start = 0 x_addr_start = 0 0 0/2 0/4 1 1/3 1/5 2 3 4 4/6 5 5/7 6 7 8 8/10 8/12 9 9/11 9/13 10 11 12 12/14 13 13/15 14 15
ar0542 www. onsemi.com 30 programming restrictions when binning binning requires different sequencing of the pixel array and imposes different timing limits on the operation of the sensor. in particular, xy-binning requires two read operations from the pixel array for each line of output data, which has the effect of increasing the minimum line blanking time. the smia specification cannot accommodate this variation because its parameter limit registers are defined as being static. as a result, when xy-binning is enabled, some of the programming limits declared in the parameter limit registers are no longer valid. in addition, the default values for some of the manufacturer-specific registers need to be reprogrammed. see section ?minimum frame time?, section ?minimum row time?, and section ?fine integration time limits?. table 15. readout modes readout modes x_odd_inc, y_odd_inc xy_bin 2x skip 3 0 2x bin 3 1 4x skip 7 0 2x skip + 2x bin 7 1 scaler scaling is a ?zoom out? operation to reduce the size of the output image while covering the same extent as the original image. each scaled output pixel is calculated by taking a weighted average of a group of input pixels which is composed of neighboring pixels. the input and output of the scaler is in bayer format. when compared to skipping, scaling is advantageous because it uses all pixel values to calculate the output image which helps avoid aliasing. also, it is also more convenient than binning because the scale factor varies smoothly and the user is not limited to certain ratios of size reduction. the ar0542 sensor is capable of horizontal scaling and full (horizontal and vertical) scaling. (scale factor scale_n scale_m 16 scale_m ) (eq. 5) the scaling factor , programmable in 1/16 steps, is used for horizontal and vertical scalers. the scale factor is determined by: ? n, which is fixed at 16 ? m, which is adjustable with register r0x0404 ? legal values for m are 16 through 256, giving the user the ability to scale from 1:1 (m = 16) to 1:16 (m = 256). for example, when horizontal and vertical scaling is enabled for a 1:2 scale factor, an image is reduced by half in both the horizontal and vertical directions. this results in an output image that is one-fourth of the original image size. this can be achieved with the following register settings: r0x0400 = 0x0002 // horizontal and vertical scaling mode r0x0402 = 0x0020 // scale factor m = 32 frame rate control the formulas for calculating the frame rate of the ar0542 are shown below. the line length is programmed directly in pixel clock periods through register line_length_pck. for a specific window size, the minimum line length can be found from in equation 6: minimum line_length_pck x_addr_end x_addr_start 1 subsampling factor min_line_blanking_pck (eq. 6) note that line_length_pck also needs to meet the minimum line length requirement set in register min_line_length_pck. the row time can either be limited by the time it takes to sample and reset the pixel array for each row, or by the time it takes to sample and read out a row. values for min_line_blanking_pck are provided in ?minimum row time?. the frame length is programmed directly in number of lines in the register frame_line_length. for a specific window size, the minimum frame length can be found in equation 7: minimum frame_length_lines y_addr_end y_addr_start 1 subsampling factor min_frame_blanking_lines (eq. 7) the frame rate can be calculated from these variables and the pixel clock speed as shown in equation 8: frame rate vt_pixel_clock_mhz 1 10 6 line_length_pck frame_length_lines (eq. 8) if coarse_integration_time is set larger than frame_length_lines the frame size will be expanded to coarse_integration_time + 1.
ar0542 www. onsemi.com 31 minimum row time the minimum row time and blanking values with default register settings are shown in table 16. table 16. minimum row time and blanking numbers no row binning row binning row_speed[2:0] 1 2 4 1 2 4 min_line_blanking_pck 0x044e 0x02b6 0x01e8 0x073c 0x040c 0x0274 min_line_length_pck 0x0590 0x03f8 0x0330 0x0940 0x0550 0x03b8 in addition, enough time must be given to the output fifo so it can output all data at the set frequency within one row time. there are therefore three checks that must all be met when programming line_length_pck: ? line_length_pck > min_line_length_pck in table 16. ? line_length_pck > (x_addr_end ? x_addr_start + x_odd_inc)/((1+x_odd_inc)/2) + min_line_blanking_pck in table 16. ? the row time must allow the fifo to output all data during each row. that is, line_length_pck > (x_output_size * 2 + 0x005e) * ?vt_pix_clk period? / ?op_pix_clk period? minimum frame time the minimum number of rows in the image is 2, so min_frame_length_lines will always equal (min_frame_blanking_lines + 2). table 17. minimum frame time and blanking numbers no row binning row binning min_frame_blanking_lines 0x004d 0x0049 min_frame_length_lines 0x005d 0x0059 integration time the integration (exposure) time of the ar0542 is controlled by the fine_integration_time and coarse_integration_time registers. the limits for the fine integration time are defined by: fine_integration_time_min fine_integration_time (line_length_pck fine_integration_time_max_margin) (eq. 9) the limits for the coarse integration time are defined by: coarse_integration_time_min coarse_integration_time (eq. 10) the actual integration time is given by: integration_time ( (coarse_integration_time line_length_pck) fine_integration_time ) (vt_pix_clk_freq_mhz 10 6 ) (eq. 11) it is required that: coarse_integration_time (frame_length_lines coarse_integration_time_max_margin) (eq. 12) if this limit is broken, the frame time will automatically be extended to coarse_integration_time + coarse_integration_time_max_margin to accommodate the larger integration time. in binning mode, frame_length_lines should be set larger than coarse_integration_time by at least 3 to avoid column imbalance artifact.
ar0542 www. onsemi.com 32 fine integration time limits the limits for the fine_integration_time can be found from fine_integration_time_min and fine_integration_time_max_margin . values for different mode combinations are shown in table 18. table 18. fine_integration_time limits no row binning row binning row_speed[2:0] 1 2 4 1 2 4 fine_integration_time_min 0x02ce 0x0178 0x006e 0x0570 0x02c8 0x00c2 fine_integration_time_max_margin 0x0159 0x00ad 0x00ad 0x02b9 0x015d 0x0149 fine_correction for the fine_integration_time limits, the fine_correction constant will change with the pixel clock speed and binning mode. it is necessary to change fine_correction (r0x3010) when binning is enabled or the pixel clock divider (row_speed[2:0]) is used. the corresponding fine_correction values are shown in table 19. table 19. fine_correction values no row binning row binning row_speed[2:0] 1 2 4 1 2 4 fine_correction 0x00a0 0x004a 0x001f 0x0140 0x009a 0x0047 flash timing control the ar0542 supports both xenon and led flash timing through the flash output signal. the timing of the flash signal with the default settings is shown in figure 28 (xenon) and figure 29 (led). the flash and flash_count registers allow the timing of the flash to be changed. the flash can be programmed to fire only once, delayed by a few frames when asserted, and (for xenon flash) the flash duration can be programmed. enabling the led flash will cause one bad frame, where several of the rows only have the flash on for part of their integration time. this can be avoided either by first enabling mask bad frames (write reset_register[9] = 1) before the enabling the flash or by forcing a restart (write reset_register[1] = 1) immediately after enabling the flash; the first bad frame will then be masked out, as shown in figure 29. read-only bit flash[14] is set during frames that are correctly integrated; the state of this bit is shown in figures 28 and figure 29. figure 28. xenon flash enabled frame_valid flash strobe state of triggered bit (r0x3046 ? 7[14])
ar0542 www. onsemi.com 33 figure 29. led flash enabled note: an option to invert the flash output signal through r0x3046[7] is also available. bad frame is masked frame_valid flash strobe state of triggered bit (flash[14]) flash enabled bad frame good frame good frame flash disabled during this frame is masked during this frame analog gain the following sections describe the on semiconductor gain model for ar0542 and the different gain stages and gain control. using per-color or global gain control the read-only analogue_gain_capability register returns a value of ?1,? indicating that the ar0542 provides per-color gain control. however, the ar0542 also provides the option of global gain control. per-color and global gain control can be used interchangeably. a write to a global gain register is aliased as a write of the same data to the four associated color-dependent gain registers. a read from a global gain register is aliased to a read of the associated greenr gain register. table 20. gain registers register bits default name frame sync?d bad frame 12382 r0x305e 15:0 0x1050 global_gain (r/w) n n 15:12 0x0001 digital_gain digital gain. legal values 1 ? 7. 11:10 0x0000 col_gain this is the column gain valid values for bits[11:10] are: 00: 1x 01: 3x 10: 2x 11: 4x y y 9:8 0x0000 asc1_gain this is the asc1 gain valid values for bits[9:8] are: 00: 1x 01: 1.3x 10: 2x 11: 4x 7 0x0000 reserved y n 6:0 0x0050 initial_gain initial gain = bits [6:0] * 1/32. gain = column gain*asc1 gain* initial_gain y y
ar0542 www. onsemi.com 34 on semiconductor gain model the on semiconductor gain model uses these registers to set the analog gain: ? global_gain ? green1_gain ? red_gain ? blue_gain ? green2_gain the ar0542 uses 11 bits analog gain control. the analog gain is given by: total gain column_gain asc1_gain initial_gain (eq. 13) color _gain[11 : 10] color _gain[9 : 8] color _gain[6 : 0] 32 table 21. valid values column_gain(_gain[11:10]) asc_gain(_gain[9:8]) 2?b00 1x 1x 2?b01 3x 1.3x 2?b10 2x 2x 2?b11 4x ? as a result, the step size varies depending upon which range the gain is in. many of the possible gain settings can be achieved in different ways. however, the recommended gain setting is to use the column_gain as much as possible instead of using asc1_gain and initial_gain for the desired gain setting, which will result lower noise. for the fine step, the initial gain should be used with column_gain and asc1_gain. the recommended minimum analog gain for ar0542 is 1.6x(r0x305e = 0x1 127). table 22 provides the gain usage table that is a guide to program a specific gain value while optimizing the noise performance from the sensor. table 22. gain usage total gain column gain asc1 gain initial gain 1.0 gain < 1.33 1 1 1.0 init < 1.33 1.33 gain < 2.0 1 1.33 1.0 init < 1.50 2.0 gain < 2.66 2 1 1.0 init < 1.33 2.66 gain < 3.0 2 1.33 1.0 init < 1.15 3.0 gain < 4.0 3 1 1.0 init < 1.33 4.0 gain < 5.3 4 1 1.0 init < 1.33 5.3 gain < 8.0 4 1.33 1.0 init < 1.50 8.0 gain < 32.0 4 2 1.0 init < 4.0
ar0542 www. onsemi.com 35 sensor core digital data path test patterns the ar0542 supports a number of test patterns to facilitate system debug. test patterns are enabled using test_pattern_mode (r0x0600?1). the test patterns are listed in table 23. table 23. test patterns test_pattern_mode description 0 normal operation: no test pattern 1 solid color 2 100% color bars 3 fade-to-gray color bars 4 pn9 link integrity pattern (only on sensors with serial interface) 256 walking 1s (10-bits) 257 walking 1s (8-bits) test patterns 0?3 replace pixel data in the output image (the embedded data rows are still present). test pattern 4 replaces all data in the output image (the embedded data rows are omitted and test pattern data replaces the pixel data). for all of the test patterns, the ar0542 registers must be set appropriately to control the frame rate and output timing. this includes: ? all clock divisors ? x_addr_start ? x_addr_end ? y_addr_start ? y_addr_end ? frame_length_lines ? line_length_pck ? x_output_size ? y_output_size effect of data path processing on test patterns test patterns are introduced early in the pixel data path. as a result, they can be af fected by pixel processing that occurs within the data path. this includes: ? noise cancellation ? black pedestal adjustment ? lens and color shading correction these effects can be eliminated by the following register settings: ? r0x3044?5[10] = 0 ? r0x30c0?1[0] = 1 ? r0x30d4?5[15] = 0 ? r0x31e0?1[0] = 0 ? r0x3180?1[15] = 0 ? r0x301a?b[3] = 0 (enable writes to data pedestal) ? r0x301e?f = 0x0000 (set data pedestal to ?0?) ? r0x3780[15] = 0 (turn off lens/color shading correction) solid color test pattern in this mode, all pixel data is replaced by fixed bayer pattern test data. the intensity of each pixel is set by its associated test data register (test_data_red, test_data_greenr, test_data_blue, test_data_greenb). 100% color bars test pattern in this test pattern, shown in figure 30, all pixel data is replaced by a bayer version of an 8-color, color-bar chart (white, yellow, cyan, green, magenta, red, blue, black). each bar is 1/8 of the width of the pixel array (2592/8 = 324 pixels). the pattern repeats after 8 * 324 = 2592 pixels. each color component of each bar is set to either 0 (fully off) or 0x3ff (fully on for 10-bit data). the pattern occupies the full height of the output image. the image size is set by x_addr_start, x_addr_end, y_addr_start, y_addr_end and may be af fected by the setting of x_output_size, y_output_size. the color-bar pattern is disconnected from the addressing of the pixel array, and will therefore always start on the first visible pixel, regardless of the value of x_addr_start. the number of colors that are visible in the output is dependent upon x_addr_end ? x_addr_start and the setting of x_output_size: the width of each color bar is fixed at 324 pixels. the effect of setting horizontal_mirror in conjunction with this test pattern is that the order in which the colors are generated is reversed: the black bar appears at the left side of the output image. any pattern repeat occurs at the right side of the output image regardless of the setting of horizontal_mirror. the state of vertical_flip has no effect on this test pattern. the effect of subsampling, binning and scaling of this test pattern is undefined. test patterns should be analyzed at full resolution only.
ar0542 www. onsemi.com 36 figure 30. 100 percent color bars test pattern horizontal mirror = 0 horizontal mirror = 1 fade-to-gray color bars test pattern in this test pattern, shown in figure 31, all pixel data is replaced by a bayer version of an 8-color, color-bar chart (white, yellow, cyan, green, magenta, red, blue, black). each bar is 1/8 of the width of the pixel array (2592/8 = 324 pixels). the test pattern repeats after 2592 pixels. each color bar fades vertically from zero or full intensity at the top of the image to 50 percent intensity (mid-gray) on the last row of the pattern. each color bar is divided into a left and a right half, in which the left half fades smoothly and the right half fades in quantized steps. the speed at which each color fades is dependent on the sensor?s data width and the height of the pixel array. we want half of the data range (from 100 or 0 to 50 percent) dif ference between the top and bottom of the pattern. because of the bayer pattern, each state must be held for two rows. the rate-of-fade of the bayer pattern is set so that there is at least one full pattern within a full-sized image for the sensor. factors that affect this are the resolution of the adc (10-bit or 12-bit) and the image height. the image size is set by x_addr_start, x_addr_end, y_addr_start, y_addr_end and may be af fected by the setting of x_output_size, y_output_size. the color-bar pattern starts at the first column in the image, regardless of the value of x_addr_start. the number of colors that are visible in the output is dependent upon x_addr_end ? x_addr_start and the setting of x_output_size: the width of each color bar is fixed at 324 pixels. the effect of setting horizontal_mirror or vertical_flip in conjunction with this test pattern is that the order in which the colors are generated is reversed: the black bar appears at the left side of the output image. any pattern repeat occurs at the right side of the output image regardless of the setting of horizontal_mirror. the effect of subsampling, binning, and scaling of this test pattern is undefined. t st patterns should be analyzed at full resolution only.
ar0542 www. onsemi.com 37 figure 31. fade-to-gray color bars test pattern horizontal mirror = 0, vertical flip = 0 horizontal mirror = 0, vertical flip = 1 horizontal mirror = 1, vertical flip = 1 horizontal mirror = 1, vertical flip = 0 pn9 link integrity pattern the pn9 link integrity pattern is intended to allow testing of a serial pixel data interface. unlike the other test patterns, the position of this test pattern at the end of the data path means that it is not affected by other data path corrections (row noise, pixel defect correction and so on). this test pattern provides a 512-bit pseudo-random test sequence to test the integrity of the serial pixel data output stream. the polynomial x 9 + x 5 + 1 is used. the polynomial is initialized to 0x1ff at the start of each frame. when this test pattern is enabled: ? the embedded data rows are disabled and the value of frame_format_decriptor_1 changes from 0x1002 to 0x1000 to indicate that no rows of embedded data are present. ? the whole output frame, bounded by the limits programmed in x_output_size and y_output_size, is filled with data from the pn9 sequence. ? the output data format is (effectively) forced into raw10 mode regardless of the state of the ccp_data_format register. before enabling this test pattern the clock divisors must be configured for raw10 operation (op_pix_clk_div = 10). this polynomial generates this sequence of 10-bit values: 0x1ff, 0x378, 0x1a1, 0x336, 0x385... on the parallel pixel data output, these values are presented 10-bits per pixclk. on the serial pixel data output, these values are streamed out sequentially without performing the raw10 packing to bytes that normally occurs on this interface. walking 1s when selected, a walking 1s pattern will be sent through the digital pipeline. the first value in each row is 0. each value will be valid for two pixels.
ar0542 www. onsemi.com 38 figure 32. walking 1s 10-bit pattern line _valid d out ( hex) 000 pixclk 000 001 004 010 040 040 001 001 002 3ff 3ff 001 002 002 004 008 008 010 020 020 080 080 100 100 200 200 000 000 figure 33. walking 1s 8-bit pattern line _valid d out ( hex) 00 pixclk 00 01 01 02 02 04 04 08 08 10 10 20 20 40 40 02 02 04 04 08 80 80 ff ff 00 00 01 01 the walking 1s pattern was implemented to facilitate assembly testing of modules with a parallel interface. the walking 1 test pattern is not active during the blanking periods; hence the output would reset to a value of 0x0. when the active period starts again, the pattern would restart from the beginning. the behavior of this test pattern is the same between full resolution and subsampling mode. raw10 and raw8 walking 1 modes are enabled by different test pattern codes. test cursors the ar0542 supports one horizontal and one vertical cursor, allowing a crosshair to be superimposed on the image or on test patterns 1?3. the position and width of each cursor are programmable in registers 0x31e8?0x31ee. both even and odd cursor positions and widths are supported. each cursor can be inhibited by setting its width to 0. the programmed cursor position corresponds to the x and y addresses of the pixel array. for example, setting horizontal_cursor_position to the same value as y_addr_start would result in a horizontal cursor being drawn starting on the first row of the image. the cursors are opaque (they replace data from the imaged scene or test pattern). the color of each cursor is set by the values of the bayer components in the test_data_red, test_data_greenr, test_data_blue and test_data_greenb registers. as a consequence, the cursors are the same color as test pattern 1 and are therefore invisible when test pattern 1 is selected. when vertical_cursor_position = 0x0fff, the vertical cursor operates in an automatic mode in which its position advances every frame. in this mode the cursor starts at the column associated with x_addr_start = 0 and advances by a step-size of 8 columns each frame, until it reaches the column associated with x_addr_start = 2584, after which it wraps (324 steps). the width and color of the cursor in this automatic mode are controlled in the usual way. the effect of enabling the test cursors when the image_orientation register is non-zero is not defined by the design specification. the behavior of the ar0542 is shown in figure 34 and the test cursors are shown as translucent, for clarity. in practice, they are opaque (they overlay the imaged scene). the manner in which the test cursors are af fected by the value of image_orientation can be understood from these implementation details: ? the test cursors are inserted last in the data path, the cursor is applied without any sensor corrections. ? the drawing of a cursor starts when the pixel array row or column address is within the address range of cursor start to cursor start + width. ? the cursor is independent of image orientation.
ar0542 www. onsemi.com 39 figure 34. test cursor behavior with image orientation readout direction vertical cursor start horizontal mirror = 0, vertical flip = 0 horizontal cursor start vertical cursor start horizontal mirror = 0, vertical flip = 1 vertical cursor start horizontal mirror = 1, vertical flip = 0 horizontal cursor start vertical cursor start horizontal mirror = 1, vertical flip = 1 readout direction readout direction readout direction horizontal cursor start horizontal cursor start digital gain integer digital gains in the range 1?7 can be programmed. pedestal this block adds the value from r0x0008?9 or (data_pedestal_) to the incoming pixel value. the data_pedestal register is read-only by default but can be made read/write by clearing the lock_reg bit in r0x301a?b. the only way to disable the effect of the pedestal is to set it to 0.
ar0542 www. onsemi.com 40 digital data path the digital data path after the sensor core is shown in figure 35. figure 35. data path scaler serial framers 2 ? 1 lane converter output bu er limiter compression registers embedded data serial pixel data interface parallel pixel data interface includes false synchronization code removal and pn9 test sequence generation interface with sensor_core embedded data format and control when the serial pixel data path is selected, the first two rows of the output image contain register values that are appropriate for the image. the 12-bit format places the data byte in bits [11:4] and sets bits [3:0] to a constant value of 0101. some register values are dynamic and may change from frame to frame. additional information on the format of the embedded data can be located in the smia specification.
ar0542 www. onsemi.com 41 timing specifications power-up sequence two power-up sequences are recommended for the ar0542 based on the xshutdown and reset_bar one-pin (pin-constrained mode) or two-pin (pin-unconstrained mode) control mode. xshutdown/reset_bar pin-constrained mode 1. turn on v dd _io power supply. 2. after 0 ? 10 ms, turn on digital reg_in (1.8 v) power supply. 3. after 0 ? 10 ms, enable extclk. 4. after 0 ? 100 ms, assert xshutdown/reset_bar (high). 5. after 1ms ? 500 ms, turn on v aa /v aa _pix power supplies. 6. wait 1 ms for internal initialization into soft standby. 7. configure pll, output and image settings to desired values. 8. set mode_select = 1 (r0x0100). 9. wait 1ms for the pll to lock before streaming state is reached. figure 36. power-up sequence with pin-constrained mode xshutdown/ reset_bar t 1 t 2 extclk operating state t 3 internal init t 4 streaming t 5 t 6 v dd _io digital reg_in (1.8 v) v aa, v aa _pix (2.8 v) hard reset soft standby pll lock note: if the ar0542 two-wire serial interface is also used for communication with other devices, the status of s data during power-up needs to be considered at the system level due to the sensor?s interaction during this time (t0 to t3) driving it to the low state; if the ar0542 two-wire serial interface is used for a dedicated point-point connection to the host, no additional considerations apply. table 24. power-up signal timing with pin-constrained mode parameter symbol min typ max unit vdd_io to digital reg_in 1.8 v t1 0 ? 10 ms digital reg_in 1.8 v to enable extclk t2 0 ? 10 ms enable extclk to hard reset assertion t3 0 ? 100 ms hard reset to vaa/vaa_pix t4 1 ? 500 ms internal initialization t5 1 ? ? ms pll lock time t6 1 ? ? ms
ar0542 www. onsemi.com 42 xshutdown/reset_bar pin-unconstrained mode 1. turn on v dd _io power supply. 2. after 0 ? 10 ms, turn on digital reg_in power supply. 3. after 1 ? 500 ms, turn on v aa /v aa _pix power supplies and enable extclk. 4. after 1 ms, assert xshutdown (high). 5. after 1 ms, assert reset_bar (high). 6. wait 1ms for internal initialization into soft standby. 7. configure pll, output and image settings to desired values. 8. set mode_select = 1 (r0x0100). 9. wait 1ms for the pll to lock before streaming state is reached. figure 37. power-up sequence with pin-unconstrained mode note: if the ar0542 two-wire serial interface is also used for communication with other devices, the status of s data during power-up needs to be considered at the system level due to the sensor?s interaction during this time (t0 to t3) driving it to the low state; if the ar0542 two-wire serial interface is used for a dedicated point-point connection to the host, no additional considerations apply. t 1 t 2 t 3 internal init t 4 streaming t 5 t 6 xshutdown/ reset_bar extclk operating state v dd _io digital reg_in (1.8 v) v aa, v aa _pix (2.8 v) hard reset soft standby pll lock table 25. power-up signal timing with pin-unconstrained mode parameter symbol min typ max unit vdd_io to digital reg_in 1.8 v t1 0 ? 10 ms digital reg_in (1.8v) to vaa, vaa_pix (2.8 v) t2 1 ? 500 ms running extclk to xshutdown assertion t3 1 ? ? ms xshutdown high to reset_bar assertion t4 1 ? ? ms internal initialization t5 1 ? ? ms pll lock time t6 1 ? ? ms
ar0542 www. onsemi.com 43 power-down sequence the recommended power-down sequence for the ar0542 is shown in figure 38. the available power supplies?v dd _io, digital 1.8 v, v aa , v aa _pix?can be turned off at the same time or have the separation specified below. 1. disable streaming if output is active by setting mode_select = 0 (r0x0100). 2. the soft standby state is reached after the current row or frame, depending on configuration, has ended. 3. assert hard reset by setting xshutdown/reset_bar to a logic ?0.? 4. turn off the v aa /v aa _pix power supplies. 5. after 0 ? 500 ms, turn off digital 1.8 v power supply. 6. after 0 ? 500 ms, turn off v dd_ io power supply. figure 38. power-down sequence turning off power supplies hard reset software standby streaming t 3 t 2 t 1 not to scale xshutdown/ reset_bar extclk v dd _io digital (1.8 v) v aa, v aa _pix table 26. power-down sequence parameter symbol min typ max unit xshutdown/reset_bar to v aa /v aa_ pix t1 0 ? 500 ms v aa /v aa_ pix to digital 1.8 v time t2 0 ? 500 ms digital 1.8 v time to v dd _io t3 0 ? 500 ms hard standby the hard standby state is reached by the assertion of the xshutdown pad. there are two hard standby entering and exiting sequences for the ar0542 based on the xshutdown and reset_bar one-pin (pin-constrained mode) or two-pin (pin-unconstrained mode) control mode. register values are not retained by this action, and will be returned to their default values once the sensor enters the hard standby state. the details of the sequence of the sequence for entering hard standby and exiting f rom hard standby are described below and shown in figure 40 and 41. xshutdown/reset_bar pin-constrained mode < entering hard standby > 1. disable streaming if output is active by setting mode_select = 0 (r0x0100). 2. the soft standby state is reached after the current row or frame, depending on configuration, has ended. 3. de-assert xshutdown/reset_bar (low) to enter the hard standby. 4. the sensor remains in hard standby state if xshutdown/reset_bar remains in the logic ?0? state.
ar0542 www. onsemi.com 44 < exiting hard standby > 1. turn off vaa/vaa_pix power-supplies and enable extclk if it was disabled. 2. after 1ms, assert xshutdown/reset/bar (high). 3. after 1ms, turn on vaa/vaa_pix power-supplies. 4. follow the pin-constrained power-up sequence from step 6 to 9 for output streaming. figure 39. hard standby with pin-constrained mode xshutdown/ extclk operating state t 3 streaming reset_bar mode_select r0x0100 streaming logic ? 1 ? internal init logic ? 0 ? logic ? 1 ? t 1 t 2 hard reset soft standby pll lock soft standby hard standby v aa, v aa _pix (2.8 v) table 27. hard standby with pin-constrained mode parameter symbol min typ max unit enter soft standby to xshutdown/ reset_bar de-assertion t1 1 ? ? ms turn off v aa /v aa _pix to xshutdown/ reset_bar assertion t2 1 ? ? ms xshutdown assertion to turn on v aa /v aa _pix supplies t3 1 ? ? ms xshutdown/reset_bar pin-unconstrained mode < entering hard standby > 1. disable streaming if output is active by setting mode_select = 0 (r0x0100). 2. the soft standby state is reached after the current row or frame, depending on configuration, has ended. 3. de-assert xshutdown (low) to enter the hard standby. 4. the sensor remains in hard standby state if xshutdown remains in the logic ?0? state. < exiting hard standby > 1. de-assert reset_bar (low) and enable extclk if it was disabled. 2. after 1ms, assert xshutdown (high). 3. after 1ms, assert reset_bar (high). 4. follow the pin-unconstrained power-up sequence from step 6 to 9 for output streaming.
ar0542 www. onsemi.com 45 figure 40. hard standby with pin-unconstrained mode xshutdown extclk operating state t 3 streaming reset_bar mode_select r0x0100 streaming logic ? 1 ? internal init logic ? 0 ? logic ? 1 ? t 1 t 2 soft standby hard reset soft standby pll lock hard standby table 28. hard standby with pin-unconstrained mode parameter symbol min typ max unit enter soft standby to xshutdown de-assertion t1 1 ? ? ms reset_bar de-assertion to xshutdown assertion t2 1 ? ? ms xshutdown assertion to reset_bar assertion t3 1 ? ? ms soft standby and soft reset the ar0542 can reduce power consumption by switching to the soft standby state when the output is not needed. register values are retained in the soft standby state. once this state is reached, soft reset can be enabled optionally to return all register values to the default. the details of the sequence are described below and shown in figure 41. soft standby 1. disable streaming if output is active by setting mode_select = 0 (r0x0100). 2. the soft standby state is reached after the current row or frame, depending on configuration, has ended. soft reset 1. follow the soft standby sequence list above. 2. set software_reset = 1 (r0x0103) to start the internal initialization sequence. 3. after 2400 extclks, the internal initialization sequence is completed and the current state returns to soft standby automatically. all registers, including software_reset, return to their default values. figure 41. soft standby and soft reset extclk mode_select r0x0100 software_reset r0x0103 logic ?1? logic ?0? streaming soft st andby soft reset soft standby next row/frame logic ?0? logic ?1? logic ?0? 2400 extclks
ar0542 www. onsemi.com 46 internal vcm driver the ar0542 utilizes an internal voice coil motor (vcm) driver. the vcm functions are register-controlled through the serial interface. there are two output ports, vcm_out and gndio_vcm, which would connect directly to the af actuator. take precautions in the design of the power supply routing to provide a low impedance path for the ground return. appropriate filtering would also be required on the actuator supply. typical values would be a 0.1 f and 10 f in parallel. figure 42. vcm driver typical diagram ar0542 vcm_out gndio_vcm vcm vvcm 10 f 0.1 f d gnd table 29. vcm driver typical characteristic parameter minimum typical maximum units vcm_out voltage at vcm current sink 2.5 2.8 3.3 v wvcm voltage at vcm actuator 2.5 2.8 3.3 v inl relative accuracy ? 1.5( ) 4( ) lsb res resolution ? 8 ? bits dnl differential nonlinearity ? 1 ? 1 lsb ivcm output current 88 100 110 ma
ar0542 www. onsemi.com 47 spectral characteristics figure 43. quantum efficiency 0 5 10 15 20 25 30 35 40 45 50 55 400 450 500 550 600 650 700 750 r gr gb b 800 quantum efficiency (%) wavelength (nm) note: on semiconductor recommends 670 5nm ir cut filter for ar0542. refer to table 30 for the ircf specification. table 30. recommended ir cut limits wavelength recommended limits < 400 nm not specified 400 ? 650 nm > 90% cut-off wavelength 670 5 nm 720 ? 900 nm equal or less than 2% 900 ? 1000 nm equal or less than 0.1% 1000 ? 1050 nm equal or less than 0.03% 1050 ? 1150 nm equal or less than 0.05% > 1150nm not specified
ar0542 www. onsemi.com 48 cra vs. image height plot image height cra (deg) figure 44. chief ray angle (cra) vs. image height 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 0 102030405060708090100110 image he ight (%) cra (deg) 0 0 0 5 0.113 2.19 10 0.227 4.33 15 0.340 6.43 20 0.454 8.50 25 0.567 10.55 30 0.680 12.57 35 0.794 14.52 40 0.907 16.39 45 1.021 18.15 50 1.134 19.76 55 1.247 21.20 60 1.361 22.43 65 1.474 23.44 70 1.588 24.21 75 1.701 24.74 80 1.814 25.03 85 1.928 25.11 90 2.041 25.01 95 2.155 24.80 100 2.268 24.55 electrical characteristics two-wire serial register interface the electrical characteristics of the two-wire serial register interface (s clk , s data ) are shown in figure 45 and table 31, ?two-wire serial interface electrical characteristics,?. the s clk and s data signals feature fail-safe input protection, schmitt trigger input, and suppression of input pulses of less than 50 ns. figure 45. two-wire serial bus timing parameters sr s ps t srts t stps t sds t sdh t sdv t srth t f t r 9 th clock t buf 1 st clock 9 th clock s data sclk s data s clk t low thigh // // // // // // t acv 30% 30% 30% 30% 30% 30% 30% 30% 30% 70% 70% 70% 70% 70% 70% 70% 70% 70% 70% 70% 70% 30% note: read sequence: for an 8-bit read, read waveforms start after the write command and register addresses are issued.
ar0542 www. onsemi.com 49 table 31. two-wire serial interface electrical characteristics ( f extclk = 24 mhz; reg_in = 1.8 v; v dd _tx = 1.8 v; v dd _io = 1.8 v; v aa = 2.8 v; v aa _pix = 2.8 v; output load = 68.5 pf; t j = 70 c) symbol parameter condition min typ max unit v il input low voltage 0.85 0.898 0.96 v i i l input leakage current no pull up resistor; v in = v dd _io or d gnd 10 14 a v ol output low voltage at specified 2 ma 0 0.054 0.58 v i ol output low current at specified v ol 0.1 v 6 ma c in input pad capacitance 6 pf c load load capacitance n/a pf table 32. two ? wire serial interface timing specification symbol parameter min max unit f sclk s clk frequency 0 400 khz t high s clk high period 0.6 s t low s clk low period 1.3 s t srts start setup time 0.6 s t srth start hold time 0.6 s t sds data setup time 100 ns t sdh data hold time 0 (note 1) s t sdv data valid time 0.9 s t acv data valid acknowledge time 0.9 s t stps stop setup time 0.6 s t buf bus free time between stop and start 1.3 s t r s clk and s data rise time 300 n s t f s clk and s data fall time 300 ns 1. maximum t sdh could be 0.9 s, but must be less than maximum of t sdv and t acv by a transition time. figure 46. parallel data output timing diagram note: pll disabled for t cp. extclk pixclk t r t f t extclk data[9:0] frame_valid/ line_valid note: frame_valid negation trails line_valid negation by 6 pixclks. t cp t pfl t pll t pd t pd t pfh t plh pxl_0 pxl_1 pxl_2 pxl_n note: frame_valid assertion leads line_valid assertion by 6 pixclk periods
ar0542 www. onsemi.com 50 extclk the electrical characteristics of the extclk input are shown in table 33. the extclk input supports an ac-coupled sine-wave input clock or a dc-coupled square-wave input clock. if extclk is ac-coupled to the ar0542 and the clock is stopped, the extclk input to the ar0542 must be driven to ground or to v dd_ io. failure to do this will result in excessive current consumption within the extclk input receiver. table 33. electrical characteristics (extclk) ( f extclk = 24 mhz; f pixclk = 84 mhz; reg_in = 1.8 v; v dd _tx = 1.8 v; v dd _io = 1.8 v; v aa = 2.8 v; v aa _pix = 2.8 v; output load = 68.5 pf; t j = 70 c) symbol parameter condition min typ max unit f extclk1 input clock frequency pll enabled 6 27 mhz textclk1 input clock period pll enabled 37 167 ns t r input clock rise slew rate 2.9 8* ns t f input clock fall slew rate 2.7 8* ns v in_ac input clock minimum voltage swing (ac coupled) 0.5 vpp v in_dc input clock maximum voltage swing (dc coupled) 2.3 v f clkmax(ac) input clock signaling frequency (low amplitude) v in = v in_ac (min) 12 mhz f clkmax(dc) input clock signaling frequency (full amplitude) v in = v dd_ io 27 mhz clock duty cycle 35 50 65 % t jitter input clock jitter cycle-to-cycle 600 ps t lock pll vco lock time 0.2 1 ms c in input pad capacitance 3 pf i ih input high leakage current 1.36 1.89 3 ma v ih input high voltage 1.26 2.3 v v il input low voltage ? 0.5 0.5 v *assuming 12 mhz input clock. parallel pixel data interface the electrical characteristics of the parallel pixel data interface (fv, lv, d out[9:0 ], pixclk, shutter, and flash outputs) are shown in table 34. table 34. electrical characteristics (parallel pixel data interface) ( f extclk = 24 mhz; f pixclk = 84 mhz; reg_in = 1.8 v; v dd _tx = 1.8 v; v dd _io = 1.8 v; v aa = 2.8 v; v aa _pix = 2.8 v; output load = 68.5 pf; t j = 70 c) symbol parameter condition min typ max unit v oh output high voltage ? v v ol output low voltage ? v i oh output high current ? ma i ol output low current ? ma i o z tri ? state output leakage current ? ma t cp extclk to pixclk propagation delay pll bypass, extclk = 27 mhz 26.519 ns output pin slew (rising) c load = 25 pf 1.4 v/ns output pin slew (falling) c load = 250 pf 1.5 v/ns t pd pixclk to data valid pll bypass, extclk = 27 mhz 1 ns f pixclk pixclk frequency default 48 mhz
ar0542 www. onsemi.com 51 table 34. electrical characteristics (parallel pixel data interface) (continued) ( f extclk = 24 mhz; f pixclk = 84 mhz; reg_in = 1.8 v; v dd _tx = 1.8 v; v dd _io = 1.8 v; v aa = 2.8 v; v aa _pix = 2.8 v; output load = 68.5 pf; t j = 70 c) unit max typ min condition parameter symbol t pfh pixclk to fv high pll bypass, extclk = 27 mhz 1 ns t plh pixclk to lv high pll bypass, extclk = 27 mhz 1 ns t pfl pixclk to fv low pll bypass, extclk = 27 mhz 1 ns t pll pixclk to lv low pll bypass, extclk = 27 mhz 1 ns serial pixel data interface the electrical characteristics of the serial pixel data interface (clk_p, clk_n,data0_p, data1_p, data0_n, and data1_n) are shown in table 35 and table 36. to operate the serial pixel data interface within the electrical limits of the csi-2 specification, v dd_ io (i/o digital voltage) is restricted to operate in the range 1.7?1.9 v. all mipi specifications are with sensor operation using on-chip internal regulator. table 35. hs transmitter dc specifications symbol parameter min nom max unit v cmtx (note 1) hs transmit static common-mode voltage 150 200 250 mv v cmtx (1,0) (note 2) v cmtx mismatch when output is differential ? 1 or differential ? 0 5 mv v od (note 1) hs transmit differential voltage 140 200 270 mv v od (note 2) v od mismatch when output is differential ? 1 or differential ? 0 10 mv v ohhs (note 1) hs output high voltage 360 mv z os single ended output impedance 40 50 62.5 | zos| single ended ouput impedance mismatch 20 % 1. value when driving into load impedance anywhere in the z id range. 2. it is recommended that the implementer minimize v od and v cmtx(1,0) in order to minimize radiation and optimize signal integrity. table 36. hs transmitter ac specifications symbol parameter min nom max unit v cmtx (hf) hs transmit static common-mode voltage 15 mv rms v cmtx (lf) v cmtx mismatch when output is differential ? 1 or differential ? 0 25 mv peak t r and t f 20% ? 80% rise time and fall time (note 2) 0.3 ui 150 ps 1. ui is equal to 1/(2*fh). 2. excess capacitance not to exceed 4 pf on each pin. table 37. lp transmitter dc specifications symbol parameter min nom max unit v oh hs transmit static common-mode voltage 1.1 1.2 1.3 v v ol v cmtx mismatch when output is differential ? 1 or differential ? 0 ? 50 50 mv z olp 20% ? 80% rise time and fall time (note 1) 110 1. though no maximum value for z olp is specified, the lp transmitter output impedance shall ensure the t rlp /t flp is met.
ar0542 www. onsemi.com 52 table 38. lp transmitter ac specifications parameter description min max unit t rlp /t flp 15% ? 80% rise time and fall time (note 1) 25 ns t reot 30% ? 85% rise time and fall time (notes 1, 5, 6) 35 ns v/ t sr slew rate @ c load = 70 pf (falling edge only), (notes 1, 3, 7, 8) 150 mv/ns slew rate @ c load = 70 pf (rising edge only), (notes 1, 2, 3) mv/ns 1. c load includes the low-frequency equivalent transmission line capacitance. the capacitance of tx and rx are assumed to always be <10pf. the disturbed line capacitance can up to 50 pf for a transmission line with 2 ns delay. 2. when the ouput voltage is between 400 mv and 930 mv. 3. measured as average across any 50 v segment of the output signal transition. 4. this parameter value can be lower than t lpx due to differences in the rise vs. fall signal slopes and trip levels and mismatches between dp and dn transmitters. any lp transmitters. any lp exclusive-or pulse observed during hs eot (transition from hs level to lp ? 1) is glitch behavior. 5. the rise time of t reot starts from the hs common-level at the moment the differential amplitude drops below 70 mv, due to stopping the differential drive. 6. with an additional load capacitance c cm between 0 and 60 pf on the termination center tap at rx side of the lane. 7. this value represents a corner point in a piecewise linear curve. 8. when the output voltage is in the range specified by v pin(absmax) 9. when the output voltage is between 400 mv and 700 mv 10. when v oinst is the instantaneous output voltage, v dp or v dn in millivolts. 11. when the output voltage is between 700 mv and 930 mv high speed clock timing figure 47. high speed clock timing 1 data bit time = 1 ui ui inst (1) 1 data bit time = 1 ui ui inst (2) 1 ddr clock period = ui inst (1) + ui inst (2) clkp clkn table 39. dc electrical characteristics (control interface) parameter description min typ max unit ui instantaneous (note 1, 2) ui inst 12.5 ns 1. this value corresponds to a minimum 80 mbps data rate. 2. the minimum ui shall not be violated for any single bit period, for example any ddr half cycle within a data burst.
ar0542 www. onsemi.com 53 data clock timing specification figure 48. data clock timing 1 ui inst t clkp clkp clkn t setup t hold 0.5 ui inst + t skew reference time table 40. data-clock timing specifications parameter symbol min typ max unit data to clock skew (measured at transmitter) t skew[tx] ? 0.15 0.15 ui inst 1. total silicon and package delay of 0.3*ui inst. control interfaces the electrical characteristics of the control interface (reset_bar, test, gpi0, gpi1, gpi2, and gpi3) are shown in table 41. table 41. dc electrical characteristics (control interface) ( f extclk = 24 mhz; reg_in = 1.8 v; v dd _tx = 1.8 v; v dd _io = 1.8 v; v aa = 2.8 v; v aa _pix = 2.8 v; output load = 68.5 pf; t j = 70 c) symbol parameter condition min typ max unit v ih input high voltage 1.26 2.3 v v il input low voltage ? 0.5 0.5 v i in input leakage current no pull-up resistor; v in = v dd_ io or d gnd 10 a c in input pad capacitance 3 pf
ar0542 www. onsemi.com 54 operating voltages v aa and v aa _pix must be at the same potential for correct operation of the ar0542. table 42. dc electrical definitions and characteristics ( f extclk = 24 mhz; reg_in = 1.8 v; v dd _tx = 1.8 v; v dd _io = 1.8 v; v aa = 2.8 v; v aa _pix = 2.8 v; output load = 68.5 pf; using internal regulator; t j = 70 c) symbol parameter condition min typ max unit reg_in 1.8 v supply voltage 1.7 1.8 1.9 v dd _tx phy digital voltage 1.7 1.8 1.9 v v dd_ io i/o digital voltage parallel pixel data interface 1.7 1.8 1.9 v 2.4 2.8 3.1 v v aa analog voltage 2.6 2.8 3.1 v v aa _pix pixel supply voltage 2.6 2.8 3.1 v i_regin/tx 1.8 v digital current streaming, full resolution parallel 15 fps 29 35 44 ma i dd _io(1.8v) i/o digital current 20 24 38 i dd _io(2.8) i/o digital current 30 45 67 i aa/ i aa _pix analog current 50 65 85 i_regin/tx 1.8 v digital current streaming, full resolution mipi 15 fps 24 26.5 44 ma i dd _io i/o digital current 0.007 0.04 0.08 i aa/ i aa _pix analog current 45 60 85 i_regin/tx 1.8 v digital current streaming, 1296x972 (xy_bin) resolution parallel 30 fps 21 23.5 30 ma i dd _io(1.8v) i/o digital current 12 13.5 16 i dd _io(2.8) i/o digital current 15 22 31 i aa/ i aa _pix analog current 50 65 85 i_regin/tx 1.8 v digital current streaming, 1296x972 (xy_bin) resolution mipi 30 fps 15 18.5 30 ma i dd _io i/o digital current 0.007 0.03 0.08 i aa/ i aa _pix analog current 50 65 85 hard standby (clock on at 24 mhz) standby current when asserting xshutdown signal analog current 0.3 1 4 a digital current 1.5 2 6 a hard standby (clock off) analog current 0.3 1 4 a digital current 1.5 2 6 a soft standby (clock on at 24 mhz) standby current when asserting r0x100 = 1 analog current 15 41 90 a digital current 4 4.8 7.5 ma soft standby (clock off) analog current 15 41 90 a digital current 3.5 4.2 7 ma 1. digital current includes reg_in, as the regulator is still operating in soft standby mode.
ar0542 www. onsemi.com 55 absolute maximum ratings table 43. absolute maximum values symbol parameter min max unit v dd 1v8(reg _ in ) 1.8 v digital voltage ? 0.3 2.1 v v dd_ tx phy digital voltage ? 0.3 2.1 v v dd_ io i/o digital voltage ? 0.3 3.5 v v aa analog supply voltage ? 0.3 3.5 v v aa_ pix pixel supply voltage ? 0.3 3.5 v t_op operating temperature measured at junction ? 30 70 c t_stg storage temperature ? 40 85 c stresses exceeding those listed in the maximum ratings table may damage the device. if any of these limits are exceeded, device function ality should not be assumed, damage may occur and reliability may be affected. smia and mipi specification reference the sensor design and this documentation is based on the following reference documents: ? smia specifications: ? smia 1.0 part 1: functional specification (version 1.0 dated 30 june 2004) ? smia 1.0 part 1: functional specification ecr0001 (version 1.0 dated 11 feb 2005) ? mipi specifications: ? mipi alliance standard for csi-2 version 1.0 ? mipi alliance specification for d-phy version 1.00.00 ? 14 may 2009 on semiconductor and are trademarks of semiconductor components industries, llc dba on semiconductor or its subsidiaries i n the united states and/or other countries. on semiconductor owns the rights to a number of patents, trademarks, copyrights, trade secrets, and other intellectual property . a listing of on semiconductor?s product/patent coverage may be accessed at www.onsemi.com/site/pdf/patent ? marking.pdf . on semiconductor reserves the right to make changes without further notice to any products herein. on semiconductor makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does o n semiconductor assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including wi thout limitation special, consequential or incidental damages. buyer is responsible for its products and applications using on semiconductor products, including compliance with all laws, reg ulations and safety requirements or standards, regardless of any support or applications information provided by on semiconductor. ?typical? parameters which may be provided in on semiconductor data sheets and/or specifications can and do vary in dif ferent applications and actual performance may vary over time. all operating parameters, including ?typic als? must be validated for each customer application by customer?s technical experts. on semiconductor does not convey any license under its patent rights nor the right s of others. on semiconductor products are not designed, intended, or authorized for use as a critical component in life support systems or any fda class 3 medical devices or medical devices with a same or similar classification in a foreign jurisdiction or any devices intended for implantation in the human body. should buyer purchase or use on semicondu ctor products for any such unintended or unauthorized application, buyer shall indemnify and hold on semiconductor and its officers, employees, subsidiaries, affiliates, and distrib utors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that on semiconductor was negligent regarding the design or manufacture of the part. on semiconductor is an equal opportunity/affirmative action employer. this literature is subject to all applicable copyright laws and is not for resale in any manner. publication ordering information n. american technical support : 800 ? 282 ? 9855 toll free usa/canada europe, middle east and africa technical support: phone: 421 33 790 2910 japan customer focus center phone: 81 ? 3 ? 5817 ? 1050 ar0542/d literature fulfillment : literature distribution center for on semiconductor 19521 e. 32nd pkwy, aurora, colorado 80011 usa phone : 303 ? 675 ? 2175 or 800 ? 344 ? 3860 toll free usa/canada fax : 303 ? 675 ? 2176 or 800 ? 344 ? 3867 toll free usa/canada email : orderlit@onsemi.com on semiconductor website : www.onsemi.com order literature : http://www.onsemi.com/orderlit for additional information, please contact your local sales representative ?

▲Up To Search▲

Price & Availability of AR0542MBSC25SUD20

	To Download AR0542MBSC25SUD20 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .